- linkend="protocol-replication">. Corresponds to the walsender protocol
+ is only possible with the
streaming-replication protocol - see
+ linkend="protocol-replication">. Corresponds to the replication protocol
command CREATE_REPLICATION_SLOT ... PHYSICAL.
Drops the physical or logical replication slot
- named
slot_name. Same as
walsender protocol
+ named
slot_name. Same as
replication protocol
command DROP_REPLICATION_SLOT.
might want to make adjustments to handle the period when
hot_standby_feedback feedback is not being provided.
For example, consider increasing max_standby_archive_delay
- so that queries are not rapidly cancelled by conflicts in WAL archive
+ so that queries are not rapidly canceled by conflicts in WAL archive
files during disconnected periods. You should also consider increasing
max_standby_streaming_delay to avoid rapid cancellations
by newly-arrived streaming WAL entries after reconnection.
void
ambuildempty (Relation indexRelation);
- Build an empty index, and write it to the initialization fork (INIT_FORKNUM)
+ Build an empty index, and write it to the initialization fork (INIT_FORKNUM)
of the given relation. This method is called only for unlogged tables; the
empty index written to the initialization fork will be copied over the main
relation fork on each server restart.
Check whether the index can support index-only scans by
returning the indexed column values for an index entry in the form of an
- IndexTuple. Return TRUE if so, else FALSE. If the index AM can never
+ IndexTuple. Return TRUE if so, else FALSE. If the index AM can never
support index-only scans (an example is hash, which stores only
the hash values not the original data), it is sufficient to set its
amcanreturn field to zero in pg_am.
keys or key/value pairs occurring within a large number of
jsonb documents (datums).
Two GIN operator classes are provided, offering different
- performance and flexibility tradeoffs.
+ performance and flexibility trade-offs.
The default GIN operator class for jsonb supports queries with
- If any parameter is NULL or an emptry string, the corresponding
+ If any parameter is NULL or an emptry string, the corresponding
environment variable (see ) is checked.
If the environment variable is not set either, then the indicated
built-in defaults are used.
An output plugin is loaded by dynamically loading a shared library with
- the output plugin's name as the library basename. The normal library
+ the output plugin's name as the library base name. The normal library
search path is used to locate the library. To provide the required output
plugin callbacks and to indicate that the library is actually an output
plugin it needs to provide a function named
various callbacks it needs to provide.
- Concurrent transactions are decoded in commit order and only changes
- belonging to a specific transaction are decoded inbetween
+ Concurrent transactions are decoded in commit order, and only changes
+ belonging to a specific transaction are decoded between
the begin and commit
callbacks. Transactions that were rolled back explicitly or implicitly
never get
Transaction Begin Callback
The required begin_cb callback is called whenever a
- start of a commited transaction has been decoded. Aborted transactions
+ start of a committed transaction has been decoded. Aborted transactions
and their contents never get decoded.
typedef void (*LogicalDecodeBeginCB) (
);
The
txn parameter contains meta information about
- the transaction, like the timestamp at which it has been committed and
+ the transaction, like the time stamp at which it has been committed and
its XID.
individual row modification inside a transaction, may it be
an INSERT, UPDATE
or DELETE. Even if the original command modified
- several rows at once the callback will be called indvidually for each
+ several rows at once the callback will be called individually for each
row.
typedef void (*LogicalDecodeChangeCB) (
|
backend_xid
xid
- Toplevel transaction identifier of this backend, if any.
+ Top-level transaction identifier of this backend, if any.
|
backend_xmin
Notice that here the planner has chosen to materialize the inner
relation of the join, by putting a Materialize plan node atop it. This
- means that the t2 indexscan will be done just once, even
+ means that the t2 index scan will be done just once, even
though the nested-loop join node needs to read that data ten times, once
for each row from the outer relation. The Materialize node saves the data
in memory as it's read, and then returns the data from memory on each
For security reasons, non-superusers are not allowed to see the SQL
- text or queryid of queries executed by other users. They can see
+ text or queryid of queries executed by other users. They can see
the statistics, however, if the view has been installed in their
database.
|
PG_DATATYPE_NAME
text
- the name of datatype related to exception
+ the name of data type related to exception
|
MESSAGE_TEXT
To initiate streaming replication, the frontend sends the
-replication parameter in the startup message. A boolean value
+replication parameter in the startup message. A Boolean value
of true tells the backend to go into walsender mode, wherein a
small set of replication commands can be issued instead of SQL statements. Only
the simple query protocol can be used in walsender mode.
Table functions may also be combined using the ROWS FROM
syntax, with the results returned in parallel columns; the number of
result rows in this case is that of the largest function result, with
- smaller results padded with NULLs to match.
+ smaller results padded with null values to match.
on master and the time on the current standby. Delays
in transfer because of networks or cascading replication configurations
may reduce the actual wait time significantly. If the system
- clocks on master and standby are not synchronised, this may lead to
+ clocks on master and standby are not synchronized, this may lead to
recovery applying records earlier than expected; but that is not a
major issue because useful settings of the parameter are much larger
than typical time deviations between servers. Be careful to allow for
This parameter is intended for use with streaming replication deployments,
- however, if the parameter is specified it will be honoured in all cases.
+ however, if the parameter is specified it will be honored in all cases.
Synchronous replication is not affected by this setting because there is
not yet any setting to request synchronous apply of transaction commits.
hot_standby_feedback will be delayed by use of this feature
arguments that are evaluated only once per aggregation rather than once
per input row. Hypothetical-set aggregates are a subclass of ordered-set
aggregates in which some of the direct arguments are required to match,
- in number and datatypes, the aggregated argument columns. This allows
+ in number and data types, the aggregated argument columns. This allows
the values of those direct arguments to be added to the collection of
aggregate-input rows as an additional hypothetical row.
If an automatically updatable view is marked with the
security_barrier property then all the view's WHERE
- conditions (and any conditions using operators which are marked as LEAKPROOF)
+ conditions (and any conditions using operators which are marked as LEAKPROOF)
will always be evaluated before any conditions that a user of the view has
added. See for full details. Note that,
due to this, rows which are not ultimately returned (because they do not
The following command-line options control the location and format of the
- output and other replication behaviour:
+ output and other replication behavior:
- Tighten checks for multi
-dimensional
+ Tighten checks for multidimensional
linkend="arrays">array input (Bruce Momjian)
Previously an input array string that started with a single-element
- array dimension could later contain multi-dimensional segments,
+ array dimension could later contain multidimensional segments,
e.g. '{{1}, {2,3}}'::int[].
Rename EXPLAIN
- ANALYZE's "total runtime" output to "execution time"
+ ANALYZE's total runtime
output to execution time
(Tom Lane)
- Improve speed of acces
essing many different
+ Improve speed of accessing many different
linkend="SQL-CREATESEQUENCE">sequences in the same session
(David Rowley)
- Allow
printf-style space padding to be specified in
+ Allow
printf-style space padding to be specified in
linkend="guc-log-line-prefix">log_line_prefix
(David Rowley)
Previously only unquoted matching strings would be imported
- as NULLs.
+ as null values.
Add structured (non-text) data type (
- linkend="datatype-json">JSONB) for storing
- JSON data (Oleg Bartunov, Teodor Sigaev, Alexander
+ linkend="datatype-json">jsonb) for storing
+ JSON data (Oleg Bartunov, Teodor Sigaev, Alexander
Korotkov, Peter Geoghegan, and Andrew Dunstan)
- This allows for faster access to values in the JSON
- document and faster and more useful indexing of JSON.
- Scalar values in JSONB documents are typed as appropriate
+ This allows for faster access to values in the JSON
+ document and faster and more useful indexing of JSON.
+ Scalar values in jsonb documents are typed as appropriate
scalar SQL types.
- Add new JSON functions to allow for the construction
- of arbitrarily complex json trees (Andrew Dunstan, Laurence Rowe)
+ Add new JSON functions to allow for the construction
+ of arbitrarily complex JSON trees (Andrew Dunstan, Laurence Rowe)
Add
linkend="functions-json-processing-table">json_typeof()
- to return the data type of a JSON value (Andrew Tipton)
+ to return the data type of a json value (Andrew Tipton)
- Allow sizeof() in ecpg
+ Allow sizeof() in ECPG
C array definitions (Michael Meskes)
- Have ecpg properly handle nesting
+ Have ECPG properly handle nesting
requirements in C and
SQL mode for C-style comments (Michael Meskes)
- OID line only if an oid column exists in a table
+ OID line only if an oid column exists in a table
(Bruce Momjian)
- Previously, the presence or absence of an oid column was always
+ Previously, the presence or absence of an oid column was always
reported.
- Avoid most uses of
dlltool in
Cygwin and+ Avoid most uses of
dlltool in
Cygwin and Mingw builds (Marco Atzeri, Hiroshi Inoue)
This allows the creation of version 4
UUIDs without- requiring the installation of uuid-ossp.
+ requiring the installation of uuid-ossp.
- functions use regclass-type arguments (Satoshi Nagayasu)
+ functions use regclass-type arguments (Satoshi Nagayasu)
- While text-type arguments are still supported, they will be
+ While text-type arguments are still supported, they will be
removed in a later major release.
setting vm.nr_hugepages. To estimate the number of
necessary huge pages start
PostgreSQL without
huge pages enabled and check the VmPeak value from the
- proc filesystem:
+ proc file system:
$ head -1 /path/to/data/directory/postmaster.pid
4170
- passthrough argument for
parserSetup+ pass
-through argument for
parserSetup
The forward transition function for moving-aggregate mode is not allowed
- to return NULL as the new state value. If the inverse transition
- function returns NULL, this is taken as an indication that the inverse
+ to return null as the new state value. If the inverse transition
+ function returns null, this is taken as an indication that the inverse
function cannot reverse the state calculation for this particular input,
and so the aggregate calculation will be redone from scratch for the
current frame starting position. This convention allows moving-aggregate
no SQL-level equivalent for it. To address this case, it is possible to
declare the final function as taking extra dummy arguments
that match the input arguments of the aggregate. Such dummy arguments
- are always passed as NULLs since no specific value is available when the
+ are always passed as null values since no specific value is available when the
final function is called. Their only use is to allow a polymorphic
final function's result type to be connected to the aggregate's input
type(s). For example, the definition of the built-in
While normal aggregates can often be implemented with support
functions written in
PL/pgSQL or another
PL language, ordered-set aggregates generally have to be written in
- C, since their state values aren't definable as any SQL datatype.
+ C, since their state values aren't definable as any SQL data type.
(In the above example, notice that the state value is declared as
type internal — this is typical.)
same definition as for normal aggregates, but note that the direct
arguments (if any) are not provided. The final function receives
the last state value, the values of the direct arguments if any,
- and (if finalfunc_extra is specified) NULL values
+ and (if finalfunc_extra is specified) null values
corresponding to the aggregated input(s). As with normal
aggregates, finalfunc_extra is only really useful if the
aggregate is polymorphic; then the extra dummy argument(s) are needed
|
consistent
- determine whether value matches query condition (boolean variant)
+ determine whether value matches query condition (Boolean variant)
(optional if support function 6 is present)
4
- Like xpath_nodeset(document, query, toptag, itemtag) but result omits toptag.
+ Like xpath_nodeset(document, query, toptag, itemtag) but result omits toptag.
Development of this module was sponsored by Torchbox Ltd. (www.torchbox.com).
- It has the same BSD licence as PostgreSQL.
+ It has the same BSD license as PostgreSQL.
projects / postgresql.git / commitdiff