Thread
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Doc: Fix punctuation errors
- 80b23bf5b858 14.17 landed
- 9efd78ef6b09 15.12 landed
- d29bf192e549 16.8 landed
- 412047f19fcb 13.20 landed
- fa761d9c7137 17.4 landed
- 0bc34ad69204 18.0 landed
-
Fix punctuation errors in PostgreSQL documentation
Noboru Saito <noborusai@gmail.com> — 2025-02-09T06:43:25Z
Hi, I am a member of the project translating PostgreSQL documentation into Japanese. For the translation, I check the number of sentences by periods. I found some issues in the original English documentation that I believe need to be corrected. Could you please review the attached patch file? Best regards, diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 38244409e3c..d3309a02798 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -8134,7 +8134,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/monitoring.sgml b/doc/src/sgml/monitoring.sgml index edc2470bcf9..fcb7196364a 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -1148,7 +1148,7 @@ description | Waiting for a newly initialized WAL file to reach durable storage <note> <para> Extensions can add <literal>Extension</literal>, - <literal>InjectionPoint</literal>. and <literal>LWLock</literal> events + <literal>InjectionPoint</literal>, and <literal>LWLock</literal> events to the lists shown in <xref linkend="wait-event-extension-table"/> and <xref linkend="wait-event-lwlock-table"/>. In some cases, the name of an <literal>LWLock</literal> assigned by an extension will not be diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml index 46240e3f725..920204a7c86 100644 --- a/doc/src/sgml/ref/pgbench.sgml +++ b/doc/src/sgml/ref/pgbench.sgml @@ -909,7 +909,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>
-
Re: Fix punctuation errors in PostgreSQL documentation
David G. Johnston <david.g.johnston@gmail.com> — 2025-02-10T01:17:53Z
On Saturday, February 8, 2025, 斉藤登 <noborusai@gmail.com> wrote: > > I found some issues in the original English documentation that I > believe need to be corrected. > I concur on all of them. David J.
-
Re: Fix punctuation errors in PostgreSQL documentation
John Naylor <johncnaylorls@gmail.com> — 2025-02-10T11:34:28Z
On Mon, Feb 10, 2025 at 8:18 AM David G. Johnston <david.g.johnston@gmail.com> wrote: > > On Saturday, February 8, 2025, 斉藤登 <noborusai@gmail.com> wrote: >> >> >> I found some issues in the original English documentation that I >> believe need to be corrected. > > > I concur on all of them. Thanks for the patch! I will push this after the upcoming minor releases. -- John Naylor Amazon Web Services
-
Re: Fix punctuation errors in PostgreSQL documentation
John Naylor <johncnaylorls@gmail.com> — 2025-02-12T06:48:35Z
On Mon, Feb 10, 2025 at 6:34 PM John Naylor <johncnaylorls@gmail.com> wrote: > Thanks for the patch! I will push this after the upcoming minor releases. This is done. -- John Naylor Amazon Web Services