a HeapTuple> pointer stored at scan->xs_hitup>,
with tuple descriptor scan->xs_hitupdesc>. (The latter
format should be used when reconstructing data that might possibly not fit
- into an IndexTuple.) In either case,
+ into an IndexTuple>.) In either case,
management of the data referenced by the pointer is the access method's
responsibility. The data must remain good at least until the next
amgettuple>, amrescan>, or amendscan>
The pg_replication_slots
view and the
- monitoring-stats-views-table">pg_stat_replication
+ pg-stat-replication-view">pg_stat_replication
view provide information about the current state of replication slots and
streaming replication connections respectively. These views apply to both physical and
logical replication.
Increase
and
- linkend="guc-checkpoint-timeout"> ; this reduces the frequency
+ linkend="guc-checkpoint-timeout">; this reduces the frequency
of checkpoints, but increases the storage requirements of
/pg_wal>.
The optional
clause AS data_type
changes the data type of the sequence. Valid types are
- are smallint, integer,
+ smallint, integer,
and bigint.
SHARE UPDATE EXCLUSIVE lock will be taken for
fillfactor and autovacuum storage parameters, as well as the
following planner related parameters:
- effective_io_concurrency, parallel_workers, seq_page_cost
- random_page_cost, n_distinct and n_distinct_inherited.
+ effective_io_concurrency>, parallel_workers>, seq_page_cost>,
+ random_page_cost>, n_distinct> and n_distinct_inherited>.
For identity columns, the COPY FROM command will always
write the column values provided in the input data, like
- the INPUT option OVERRIDING SYSTEM
+ the INSERT option OVERRIDING SYSTEM
VALUE.
The optional
clause AS data_type
specifies the data type of the sequence. Valid types are
- are smallint, integer,
+ smallint, integer,
and bigint. bigint is the
default. The data type determines the default minimum and maximum
values of the sequence.
partitioned table. The parenthesized list of
columns or expressions forms the partition key
for the table. When using range partitioning, the partition key can
- include multiple columns or expressions (up to 32, but this limit can
- altered when building
PostgreSQL.), but for
+ include multiple columns or expressions (up to 32, but this limit can be
+ altered when building
PostgreSQL), but for
list partitioning, the partition key must consist of a single column or
expression. If no B-tree operator class is specified when creating a
partitioned table, the default B-tree operator class for the datatype will
-->
Overhaul documentation build
- process> (Alexander Lakhin, Alexander Law)
+ process> (Alexander Lakhin)
- Previously
Jade>, DSSSL,> and
+ Previously
Jade>, DSSSL>, and