Re: pg_receivewal documentation - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_receivewal documentation
Date
Msg-id 20190722014851.GC1757@paquier.xyz
Whole thread Raw
In response to Re: pg_receivewal documentation  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: pg_receivewal documentation  (Jesper Pedersen <jesper.pedersen@redhat.com>)
List pgsql-hackers
On Fri, Jul 19, 2019 at 02:04:03PM -0400, Robert Haas wrote:
> You could just say something like:
>
> Since pg_receivewal does not apply WAL, you should not allow it to
> become a synchronous standby when synchronous_commit = remote_apply.
> If it does, it will appear to be a standby which never catches up,
> which may cause commits to block.  To avoid this, you should either
> configure an appropriate value for synchronous_standby_names, or
> specify an application_name for pg_receivewal that does not match it,
> or change the value of synchronous_commit to something other than
> remote_apply.
>
> I think that'd be a lot more useful than enumerating the total-failure
> scenarios.

+1.  Thanks for the suggestions!  Your wording looks good to me.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Speed up transaction completion faster after many relations areaccessed in a transaction
Next
From: "Tsunakawa, Takayuki"
Date:
Subject: RE: Speed up transaction completion faster after many relations areaccessed in a transaction