Re: pg_receivewal documentation
Jesper Pedersen <jesper.pedersen@redhat.com>
From: Jesper Pedersen <jesper.pedersen@redhat.com>
To: Michael Paquier <michael@paquier.xyz>, Robert Haas <robertmhaas@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>,
Alvaro Herrera <alvherre@2ndquadrant.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2019-07-22T17:25:41Z
Lists: pgsql-hackers
Attachments
- v9_pgreceivewal-doc.patch (text/x-patch)
Hi, On 7/21/19 9:48 PM, Michael Paquier wrote: >> 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. +1 Here is the patch for it, with Robert as the author. Best regards, Jesper
Commits
-
Doc: Clarify interactions of pg_receivexlog with remote_apply
- 4a25ed16400c 9.6.15 landed
-
Doc: Clarify interactions of pg_receivewal with remote_apply
- 1c423463e4b9 10.10 landed
- 059e22693b23 11.5 landed
- a15a40aaaedf 12.0 landed
- fd7d387e0548 13.0 landed