postgres.git / summary / log / commit / refs

commit    0bc34ad69204dded9cd06d03c3ced656eb137dc3
Author:   John Naylor <john.naylor@postgresql.org>
Date:     Wed Feb 12 06:12:51 2025 +0000
First released in: 18.0, 13.20, 14.17, 15.12, 16.8, 17.4

    Doc: Fix punctuation errors
    
    Author: 斉藤登 <noborusai@gmail.com>
    Reviewed-by: David G. Johnston <david.g.johnston@gmail.com>
    Discussion: https://postgr.es/m/CAAM3qnL6i-BSu5rB2+KiHLjMCOXiQEiPMBvEj7F1CgUzZMooLA@mail.gmail.com
    Backpatch-through: 13


doc/src/sgml/config.sgml | 2 +- doc/src/sgml/libpq.sgml | 2 +- doc/src/sgml/ref/pgbench.sgml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 3b557ecabfb..5e4f201e099 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -8140,7 +8140,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; various purposes. The cluster name appears in the process title for all server processes in this cluster. Moreover, it is the default application name for a standby connection (see <xref - linkend="guc-synchronous-standby-names"/>.) + linkend="guc-synchronous-standby-names"/>). </para> <para> diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index e04acf1c208..c49e975b082 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -5392,7 +5392,7 @@ PGresult *PQgetResult(PGconn *conn); <literal>PGRES_PIPELINE_SYNC</literal> will be returned. The result of the next query after the synchronization point follows immediately (that is, no null pointer is returned after - the synchronization point.) + the synchronization point). </para> <note> diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml index 3f488b44d7b..ab252d9fc74 100644 --- a/doc/src/sgml/ref/pgbench.sgml +++ b/doc/src/sgml/ref/pgbench.sgml @@ -908,7 +908,7 @@ pgbench <optional> <replaceable>options</replaceable> </optional> <replaceable>d Print messages about all errors and failures (errors without retrying) including which limit for retries was exceeded and how far it was exceeded for the serialization/deadlock failures. (Note that in this - case the output can be significantly increased.). + case the output can be significantly increased.) See <xref linkend="failures-and-retries"/> for more information. </para> </listitem> [parent: bb8dff9995f2]