Re: DOCS - inactive_since field readability

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: DOCS - inactive_since field readability
Date: 2025-02-11 11:10:48
Message-ID: CAA4eK1+juemQoTVd7xKqegLH0ZUp6qibL5uyV+bS-DxwnfXgnQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 7, 2025 at 12:05 PM Peter Smith <smithpb2250(at)gmail(dot)com> wrote:
>
>
> I've had a go at rewording this paragraph in the 0002 patch.
>

The change in 0001 looks odd after seeing it in HTML format. We should
either add one empty line between two paragraphs otherwise it doesn't
appear good. Did you see multi-paragraphs in any other column
definitions?

For the 0002 patch, I find the following changes as improvements,
*
<para>
- Note that for slots on the standby
to
+ For standby slots

*
On standby, this is useful for slots
- that are being synced from a primary server (whose
- <structfield>synced</structfield> field is <literal>true</literal>)
- so they know when the slot stopped being synchronized.
to
This helps standby slots
+ track when synchronization was interrupted.

Other than that, I find the current wording okay.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Shlok Kyal 2025-02-11 11:25:15 Re: Restrict publishing of partitioned table with a foreign table as partition
Previous Message Shubham Khanna 2025-02-11 10:16:24 Re: Enhance 'pg_createsubscriber' to retrieve databases automatically when no database is provided.