+
queryid only appl
y when
linkend="guc-compute-query-id"/> is enabled. If you use an external
module instead to compute queryid, you
should refer to its documentation for details.
Connection Management Options
- By default all the open connections that postgres_fdw
- established to the foreign servers are kept in local session for re-use.
+ By default, all connections that postgres_fdw
+ establishes to foreign servers are kept open in the local session
+ for re-use.
This option controls whether postgres_fdw keeps
- the connections to the foreign server open so that the subsequent
+ the connections to the foreign server open so that subsequent
queries can re-use them. It can only be specified for a foreign server.
The default is on. If set to off,
all connections to this foreign server will be discarded at the end of
- transaction.
+ each transaction.
-
+ cuum-scale-factor" xreflabel="autovacuum_vacuum_scale_factor">
autovacuum_vacuum_scale_factor, toast.autovacuum_vacuum_scale_factor (floating point)
autovacuum_vacuum_scale_factor
-
+ cuum-cost-limit" xreflabel="autovacuum_vacuum_cost_limit">
autovacuum_vacuum_cost_limit, toast.autovacuum_vacuum_cost_limit (integer)
autovacuum_vacuum_cost_limit
If you wish to create a new superuser, you must connect as a
superuser, not merely with CREATEROLE privilege.
Being a superuser implies the ability to bypass all access permission
- checks within the database, so superuserdom should not be granted lightly.
+ checks within the database, so superuser access should not be granted lightly.
According to the SQL standard, changes made to insensitive cursors by
UPDATE ... WHERE CURRENT OF and DELETE
- ... WHERE CURRENT OF statements are visibible in that same
+ ... WHERE CURRENT OF statements are visible in that same
cursor.
PostgreSQL treats these statements like
all other data changing statements in that they are not visible in
insensitive cursors.
- If "all-frozen" is given, table corruption checks
+ If all-frozen is given, table corruption checks
will skip over pages in all tables that are marked as all frozen.
- The column of the kind of extended stats (e.g. Ndistinct) shows its status.
- NULL means that it doesn't exists. "defined" means that it was requested
- when creating the statistics.
+ The status of each kind of extended statistics is shown in a column
+ named after its statistic kind (e.g. Ndistinct).
+ "defined" means that it was requested when creating the statistics,
+ and NULL means it wasn't requested.
You can use pg_stats_ext if you'd like to know whether
ANALYZE was run and statistics are available to the
planner.
fsync, or fsync_writethrough,
the write operation moves WAL buffers to kernel cache and
issue_xlog_fsync syncs them to disk. Regardless
- of the setting of track_wal_io_timing, the numbers
+ of the setting of track_wal_io_timing, the number
of times XLogWrite writes and
issue_xlog_fsync syncs WAL data to disk are also
counted as wal_write and wal_sync
* reltypeid: OID to assign to rel's rowtype, or InvalidOid to select one
* reloftypeid: if a typed table, OID of underlying type; else InvalidOid
* ownerid: OID of new rel's owner
+ * accessmtd: OID of new rel's access method
* tupdesc: tuple descriptor (source of column definitions)
* cooked_constraints: list of precooked check constraints and defaults
* relkind: relkind for new rel
*
* We assume that VACUUM hasn't set pg_class.reltuples already, even
* during a VACUUM ANALYZE. Although VACUUM often updates pg_class,
- * exceptions exists. A "VACUUM (ANALYZE, INDEX_CLEANUP OFF)" command
+ * exceptions exist. A "VACUUM (ANALYZE, INDEX_CLEANUP OFF)" command
* will never update pg_class entries for index relations. It's also
* possible that an individual index's pg_class entry won't be updated
* during VACUUM if the index AM returns NULL from its amvacuumcleanup()
PROGRESS_CLUSTER_PHASE_FINAL_CLEANUP);
/*
- * If the relation being rebuild is pg_class, swap_relation_files()
+ * If the relation being rebuilt is pg_class, swap_relation_files()
* couldn't update pg_class's own pg_class entry (check comments in
* swap_relation_files()), thus relfrozenxid was not updated. That's
* annoying because a potential reason for doing a VACUUM FULL is a
* Once flushed we also trim the tracked buffers list down to size by removing
* the buffers created earliest first.
*
- * Callers should pass 'curr_rri' is the ResultRelInfo that's currently being
+ * Callers should pass 'curr_rri' as the ResultRelInfo that's currently being
* used. When cleaning up old buffers we'll never remove the one for
* 'curr_rri'.
*/
* that would require additional columns.
*
* See statext_compute_stattarget for details about how we compute statistics
- * target for a statistics objects (from the object target, attribute targets
+ * target for a statistics object (from the object target, attribute targets
* and default statistics target).
*/
int
* this path. E.g. the path [a][0][b] with the new value 1 will produce the
* structure {a: [{b: 1}]}.
*
- * Called is responsible to make sure such path does not exist yet.
+ * Caller is responsible to make sure such path does not exist yet.
*/
static void
push_path(JsonbParseState **st, int level, Datum *path_elems,
* than just one last element, this flag will instruct to create the whole
* chain of corresponding objects and insert the value.
*
- * JB_PATH_CONSISTENT_POSITION for an array indicates that the called wants to
+ * JB_PATH_CONSISTENT_POSITION for an array indicates that the caller wants to
* keep values with fixed indices. Indices for existing elements could be
* changed (shifted forward) in case if the array is prepended with a new value
* and a negative index out of the range, so this behavior will be prevented
seek($fh, $offset, 0)
or BAIL_OUT("seek failed: $!");
defined(syswrite($fh, $buffer, HEAPTUPLE_PACK_LENGTH))
- or BAIL_OUT("syswrite failed: $!");;
+ or BAIL_OUT("syswrite failed: $!");
return;
}
/*
* Find the median of three values. Currently, performance seems to be best
- * if the the comparator is inlined here, but the med3 function is not inlined
+ * if the comparator is inlined here, but the med3 function is not inlined
* in the qsort function.
*/
static pg_noinline ST_ELEMENT_TYPE *
* dividing line between "interactive" and "non-interactive" sources for
* error reporting purposes.
*
- * PGC_S_TEST is used when testing values to be used later ("doit" will always
- * be false, so this never gets stored as the actual source of any value).
- * For example, ALTER DATABASE/ROLE tests proposed per-database or per-user
- * defaults this way, and CREATE FUNCTION tests proposed function SET clauses
- * this way. This is an interactive case, but it needs its own source value
- * because some assign hooks need to make different validity checks in this
- * case. In particular, references to nonexistent database objects generally
+ * PGC_S_TEST is used when testing values to be used later. For example,
+ * ALTER DATABASE/ROLE tests proposed per-database or per-user defaults this
+ * way, and CREATE FUNCTION tests proposed function SET clauses this way.
+ * This is an interactive case, but it needs its own source value because
+ * some assign hooks need to make different validity checks in this case.
+ * In particular, references to nonexistent database objects generally
* shouldn't throw hard errors in this case, at most NOTICEs, since the
* objects might exist by the time the setting is used for real.
*
projects / postgresql.git / commitdiff