Re: pg_recvlogical requires -d but not described on the documentation - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: pg_recvlogical requires -d but not described on the documentation
Date
Msg-id b15ecf4f-e5af-4fbb-82c2-a425f453e0b2@oss.nttdata.com
Whole thread Raw
In response to Re: pg_recvlogical requires -d but not described on the documentation  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: pg_recvlogical requires -d but not described on the documentation
RE: pg_recvlogical requires -d but not described on the documentation
List pgsql-hackers

On 2025/03/12 14:59, David G. Johnston wrote:
> On Monday, February 24, 2025, Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com <mailto: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
apolicy that would alter the synopsis in the proposed manner.  I’d suggest leaving it alone for now and tweak any of
theoption descriptions that may need clarification.
 

I agree that the synopsis doesn't need to be updated. Attached patch clarifies
the required options for each action in the documentation. Thought?

BTW, I'm curious why --dbname isn't required for the --drop-slot action. When I ran
pg_recvlogical --drop-slot without --dbname, I got the following error:

   pg_recvlogical: error: could not establish database-specific replication connection

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: pgsql: pg_upgrade: Preserve default char signedness value from old clus
Next
From: Pavel Stehule
Date:
Subject: Re: Re: proposal: schema variables