Minor fixes in docs and error messages.

Alexander Lakhin

Discussion: https://postgr.es/m/ce7debdd-c943-d7a7-9b41-687107b27831@gmail.com
This commit is contained in:
Tom Lane 2020-09-09 11:53:39 -04:00
parent 1bf0b9c5f5
commit aa33187164
5 changed files with 16 additions and 12 deletions

View File

@ -34,14 +34,18 @@
<productname>PostgreSQL</productname> is started by including the module name in <productname>PostgreSQL</productname> is started by including the module name in
<varname>shared_preload_libraries</varname>. A module wishing to run a background <varname>shared_preload_libraries</varname>. A module wishing to run a background
worker can register it by calling worker can register it by calling
<function>RegisterBackgroundWorker(<type>BackgroundWorker *worker</type>)</function> <function>RegisterBackgroundWorker(<type>BackgroundWorker</type>
from its <function>_PG_init()</function>. Background workers can also be started *<parameter>worker</parameter>)</function>
after the system is up and running by calling the function from its <function>_PG_init()</function> function.
<function>RegisterDynamicBackgroundWorker(<type>BackgroundWorker Background workers can also be started
*worker, BackgroundWorkerHandle **handle</type>)</function>. Unlike after the system is up and running by calling
<function>RegisterBackgroundWorker</function>, which can only be called from within <function>RegisterDynamicBackgroundWorker(<type>BackgroundWorker</type>
the postmaster, <function>RegisterDynamicBackgroundWorker</function> must be *<parameter>worker</parameter>, <type>BackgroundWorkerHandle</type>
called from a regular backend or another background worker. **<parameter>handle</parameter>)</function>. Unlike
<function>RegisterBackgroundWorker</function>, which can only be called from
within the postmaster process,
<function>RegisterDynamicBackgroundWorker</function> must be called
from a regular backend or another background worker.
</para> </para>
<para> <para>

View File

@ -263,7 +263,7 @@
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term><function>inrange</function></term> <term><function>in_range</function></term>
<listitem> <listitem>
<indexterm> <indexterm>
<primary>in_range support functions</primary> <primary>in_range support functions</primary>

View File

@ -452,7 +452,7 @@
-- a message can be in one or more <quote>sections</quote> -- a message can be in one or more <quote>sections</quote>
CREATE TABLE message (mid INT PRIMARY KEY, sections INT[], ...); CREATE TABLE message (mid INT PRIMARY KEY, sections INT[], ...);
-- create specialized index with sigature length of 32 bytes -- create specialized index with signature length of 32 bytes
CREATE INDEX message_rdtree_idx ON message USING GIST (sections gist__int_ops(siglen=32)); CREATE INDEX message_rdtree_idx ON message USING GIST (sections gist__int_ops(siglen=32));
-- select messages in section 1 OR 2 - OVERLAP operator -- select messages in section 1 OR 2 - OVERLAP operator

View File

@ -272,7 +272,7 @@ AddWALInfoToBackupManifest(backup_manifest_info *manifest, XLogRecPtr startptr,
*/ */
if (!found_start_timeline) if (!found_start_timeline)
ereport(ERROR, ereport(ERROR,
errmsg("start timeline %u not found history of timeline %u", errmsg("start timeline %u not found in history of timeline %u",
starttli, endtli)); starttli, endtli));
/* Terminate the list of WAL ranges. */ /* Terminate the list of WAL ranges. */

View File

@ -3133,7 +3133,7 @@ static struct config_int ConfigureNamesInt[] =
}, },
{ {
{"autovacuum_vacuum_insert_threshold", PGC_SIGHUP, AUTOVACUUM, {"autovacuum_vacuum_insert_threshold", PGC_SIGHUP, AUTOVACUUM,
gettext_noop("Minimum number of tuple inserts prior to vacuum, or -1 to disable insert vacuums"), gettext_noop("Minimum number of tuple inserts prior to vacuum, or -1 to disable insert vacuums."),
NULL NULL
}, },
&autovacuum_vac_ins_thresh, &autovacuum_vac_ins_thresh,