Re: pg_recvlogical requires -d but not described on the documentation
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2025-03-12T05:59:09Z
Lists: pgsql-hackers
On Monday, February 24, 2025, Hayato Kuroda (Fujitsu) < kuroda.hayato@fujitsu.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.
Commits
-
Allow pg_recvlogical --drop-slot to work without --dbname.
- c68100aa4313 18.0 landed
-
doc: Clarify required options for each action in pg_recvlogical.
- dfc13428a908 18.0 landed
-
Refactor replication connection code of various pg_basebackup utilities.
- 0c013e08cfbe 9.5.0 cited