public inbox for [email protected]
help / color / mirror / Atom feedFrom: Michael Paquier <[email protected]>
To: Peter Smith <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: DOCS - typos and grammar issues across logical replication docs.
Date: Mon, 27 Apr 2026 16:18:43 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAHut+PuvY_wYLPJ4DTs7NE9Lu2ty4d-OgZAOJC-NvCM=2wwcQQ@mail.gmail.com>
References: <CAHut+PuvY_wYLPJ4DTs7NE9Lu2ty4d-OgZAOJC-NvCM=2wwcQQ@mail.gmail.com>
On Fri, Apr 24, 2026 at 03:32:24PM +1000, Peter Smith wrote:
> I fed the logical replication online documentation into my favourite
> AI tool to help me come up with the following patch that fixes many
> minor issues (e.g., spelling, grammar, inconsistencies, vagueness,
> etc.).
It is a mixed bag of changes. Some of the suggestions are correct
grammar fixes, some make things somewhat worse, some are irrelevant
(like the s/won't/will not/ or the s/please//).
- When logical replication of a table typically starts, PostgreSQL takes
- a snapshot of the table's data on the publisher database and copies it
+ Logical replication of a table typically starts by PostgreSQL taking
+ a snapshot of the table's data on the publisher database and copying it
to the subscriber. Once complete, changes on the publisher since the
This new sentence makes less sense here. And there's nothing bad with
the original.
Some of these mistakes are older than HEAD, and are user-visible, so
backpatched the most relevant ones.
Thanks.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (833B, 2-signature.asc)
download
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: DOCS - typos and grammar issues across logical replication docs.
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox