]> git.ipfire.org Git - thirdparty/postgresql.git/commitdiff
Minor fixes in docs and error messages.
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 9 Sep 2020 15:53:39 +0000 (11:53 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 9 Sep 2020 15:53:39 +0000 (11:53 -0400)
Alexander Lakhin

Discussion: https://postgr.es/m/ce7debdd-c943-d7a7-9b41-687107b27831@gmail.com

doc/src/sgml/bgworker.sgml
doc/src/sgml/btree.sgml
doc/src/sgml/intarray.sgml
src/backend/replication/backup_manifest.c
src/backend/utils/misc/guc.c

index 6e1cf121de08b4be2d1a584d949c3ecf06e9eff3..7fd673ab54ee4420a260963e07e27e578e2f772f 100644 (file)
   <productname>PostgreSQL</productname> is started by including the module name in
   <varname>shared_preload_libraries</varname>.  A module wishing to run a background
   worker can register it by calling
-  <function>RegisterBackgroundWorker(<type>BackgroundWorker *worker</type>)</function>
-  from its <function>_PG_init()</function>.  Background workers can also be started
-  after the system is up and running by calling the function
-  <function>RegisterDynamicBackgroundWorker(<type>BackgroundWorker
-  *worker, BackgroundWorkerHandle **handle</type>)</function>.  Unlike
-  <function>RegisterBackgroundWorker</function>, which can only be called from within
-  the postmaster, <function>RegisterDynamicBackgroundWorker</function> must be
-  called from a regular backend or another background worker.
+  <function>RegisterBackgroundWorker(<type>BackgroundWorker</type>
+  *<parameter>worker</parameter>)</function>
+  from its <function>_PG_init()</function> function.
+  Background workers can also be started
+  after the system is up and running by calling
+  <function>RegisterDynamicBackgroundWorker(<type>BackgroundWorker</type>
+  *<parameter>worker</parameter>, <type>BackgroundWorkerHandle</type>
+  **<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>
index 435b7cb24da94739aabe13f9cda453d8289a574a..20cabe921fb3adc40ac22f2b3269bf0efc12ad95 100644 (file)
    </listitem>
   </varlistentry>
   <varlistentry>
-   <term><function>inrange</function></term>
+   <term><function>in_range</function></term>
    <listitem>
     <indexterm>
      <primary>in_range support functions</primary>
index c8db87e97df907bfb8bd7afb3161d4cb97abf995..af44c7b2142d1d36be7e0778ef3b35d881278b35 100644 (file)
 -- a message can be in one or more <quote>sections</quote>
 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));
 
 -- select messages in section 1 OR 2 - OVERLAP operator
index b6260049271b468dcf4b0ebbc9467c2065d2c039..a43c793e2892ad1523ce42c7c24ddea34dd48436 100644 (file)
@@ -272,7 +272,7 @@ AddWALInfoToBackupManifest(backup_manifest_info *manifest, XLogRecPtr startptr,
         */
        if (!found_start_timeline)
                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));
 
        /* Terminate the list of WAL ranges. */
index de87ad6ef702877445cf6588526211b77cbb6b56..73518d9866211a89103e19d7d7319b30c0d0042e 100644 (file)
@@ -3140,7 +3140,7 @@ static struct config_int ConfigureNamesInt[] =
        },
        {
                {"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
                },
                &autovacuum_vac_ins_thresh,