| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_recvlogical requires -d but not described on the documentation |
| Date: | 2025-03-12 05:59:09 |
| Message-ID: | CAKFQuwYWVT84GM2OqRx8EqNrfzNM-zbpQ5Y2bA1dPO9jUgo_Kg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Monday, February 24, 2025, Hayato Kuroda (Fujitsu) <
kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
>
>
> OK, so I will exclude the point in the thread. The patch I've posted
> contains all of fixes
> which is required.
>
The patch fixes the synopsis and the mention of the default value. Only
the later is required. I cannot figure out a policy that would alter the
synopsis in the proposed manner. I’d suggest leaving it alone for now and
tweak any of the option descriptions that may need clarification. At least
then we remain consistent with a policy that options are never listed in
client application synopses. Which seems to be the policy that is in
force. There is discussion to better document, and possibly change these
policies, especially since server application synopses routinely violate
this no-options policy.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-03-12 06:08:34 | Re: pg_recvlogical requires -d but not described on the documentation |
| Previous Message | Dilip Kumar | 2025-03-12 05:54:02 | Re: Parallel heap vacuum |