Deduplication cannot be used in all cases due to
implementation-level restrictions. Deduplication safety is
determined when <command>CREATE INDEX</command> or
- <command>REINDEX</command> run.
+ <command>REINDEX</command> is run.
</para>
<para>
Note that deduplication is deemed unsafe and cannot be used in the
<xref linkend="sql-analyze"/>.
A zero value indicates that no statistics should be collected.
A negative value says to use the system default statistics target.
- Positive values <structfield>stxstattarget</structfield>
+ Positive values of <structfield>stxstattarget</structfield>
determine the target number of <quote>most common values</quote>
to collect.
</entry>
For example, <literal>30.1 GB</literal> will be converted
to <literal>30822 MB</literal> not <literal>32319628902 B</literal>.
If the parameter is of integer type, a final rounding to integer
- occurs after any units conversion.
+ occurs after any unit conversion.
</para>
</listitem>
unoptimized queries in your applications.
If this value is specified without units, it is taken as milliseconds.
Setting this to zero prints all statement durations.
- Minus-one (the default) disables logging statement durations.
- Only superusers can change this setting.
+ <literal>-1</literal> (the default) disables logging statement
+ durations. Only superusers can change this setting.
</para>
<para>
traffic is too high to log all queries.
If this value is specified without units, it is taken as milliseconds.
Setting this to zero samples all statement durations.
- Minus-one (the default) disables sampling statement durations.
- Only superusers can change this setting.
+ <literal>-1</literal> (the default) disables sampling statement
+ durations. Only superusers can change this setting.
</para>
<para>
<title>Producing XML Content</title>
<para>
- A set of functions and function-like expressions are available for
+ A set of functions and function-like expressions is available for
producing XML content from SQL data. As such, they are
particularly suitable for formatting query results into XML
documents for processing in client applications.
<note>
<para>
- Some of the <literal>jsonb_path_*</literal> functions have the
+ Some of the <literal>jsonb_path_*</literal> functions have a
<literal>_tz</literal> suffix. These functions have been implemented to
support comparison of date/time values that involves implicit
timezone-aware casts. Since operations with time zones are not immutable,
The functions <function>to_regclass</function>, <function>to_regcollation</function>,
<function>to_regnamespace</function>, <function>to_regoper</function>,
<function>to_regoperator</function>, <function>to_regrole</function>,
- <function>to_regproc</function>, <function>to_regprocedure</function>, and
- <function>to_regtype</function>, functions translate relation, collation, schema,
+ <function>to_regproc</function>, <function>to_regprocedure</function> and
+ <function>to_regtype</function> translate relation, collation, schema,
operator, role, function, and type names (given as <type>text</type>) to
objects of the corresponding <type>reg*</type> type (see <xref
linkend="datatype-oid"/> about the types). These functions differ from a
its default <function>PQdefaultSSLKeyPassHook</function> handler. The callback
should determine the password for the key and copy it to result-buffer
<literal>buf</literal> of size <literal>size</literal>. The string in <literal>
- buf</literal> must be null-terminated. The calback must return the length of
+ buf</literal> must be null-terminated. The callback must return the length of
the password stored in <literal>buf</literal> excluding the null terminator.
On failure, the callback should set <literal>buf[0] = '\0'</literal> and return 0.
See <function>PQdefaultSSLKeyPassHook</function> in <literal>libpq</literal>'s
</para>
<para>
- It is important to note that that the validation which is performed by
+ It is important to note that the validation which is performed by
<application>pg_validatebackup</application> does not and can not include
every check which will be performed by a running server when attempting
to make use of the backup. Even if you use this tool, you should still
a <literal>backup_manifest</literal> file in the target directory or
about anything inside <literal>pg_wal</literal>, even though these
files won't be listed in the backup manifest. Only files are checked;
- the presence or absence or directories is not verified, except
+ the presence or absence of directories is not verified, except
indirectly: if a directory is missing, any files it should have contained
will necessarily also be missing.
</para>
list_free_deep(fks);
/*
- * Any sub-constrains that are in the referenced-side of a larger
+ * Any sub-constraints that are in the referenced-side of a larger
* constraint have to be removed. This partition is no longer part of the
* key space of the constraint.
*/
* evaluation of the expression will have the same type of slot, with an
* equivalent descriptor.
*
- * Returns true if the the deforming step is required, false otherwise.
+ * Returns true if the deforming step is required, false otherwise.
*/
static bool
ExecComputeSlotInfo(ExprState *state, ExprEvalStep *op)
* Instruct the postmaster to terminate a background worker.
*
* Note that it's safe to do this without regard to whether the worker is
- * still running, or even if the worker may already have existed and been
+ * still running, or even if the worker may already have exited and been
* unregistered.
*/
void
}
/*
- * Each file's entry need to be separated from any entry that follows by a
+ * Each file's entry needs to be separated from any entry that follows by a
* comma, but there's no comma before the first one or after the last one.
* To make that work, adding a file to the manifest starts by terminating
* the most recently added line, with a comma if appropriate, but does not
/* shift forward, starting at last occupied element */
/*
- * TODO: This could be optimized to be one memcpy in may cases,
+ * TODO: This could be optimized to be one memcpy in many cases,
* excepting wrapping around at the end of ->data. Hasn't shown up
* in profiles so far though.
*/
projects / postgresql.git / commitdiff