public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Smith <[email protected]>
To: Michael Paquier <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: DOCS - typos and grammar issues across logical replication docs.
Date: Tue, 28 Apr 2026 10:42:36 +1000
Message-ID: <CAHut+Ps7-6nCt7FLE5yRS6FEnxVH-MAXx-RyfykzN=hPGP+GCg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAHut+PuvY_wYLPJ4DTs7NE9Lu2ty4d-OgZAOJC-NvCM=2wwcQQ@mail.gmail.com>
	<[email protected]>

On Mon, Apr 27, 2026 at 5:18 PM Michael Paquier <[email protected]> wrote:
>
> 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.

Hi Michael,

Thanks for pushing!

(My opinion differs about some of the rejected ones, but I am not
going to debate about them.)

======
Kind Regards
Peter Smith.
Fujitsu Australia

view thread (3+ messages)

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: <CAHut+Ps7-6nCt7FLE5yRS6FEnxVH-MAXx-RyfykzN=hPGP+GCg@mail.gmail.com>

* 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