| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Erik Rijkers <er(at)xs4all(dot)nl> |
| Subject: | Re: logical replication apply to run with sync commit off by default |
| Date: | 2017-04-07 02:32:21 |
| Message-ID: | CAMsr+YGPF7tSN7U8bYxe169btb25rS9Z_rS5hsxzHQCezySadQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7 April 2017 at 01:38, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> I think this change could use some more documentation. Under what
> circumstances would a user want to turn this back on?
The main reason is if you want to use synchronous_standby_names and
synchronous commit on the upstream. Turning sync appy back on for
logical replicas will cause them to send more timely standby status
updates, so commits on the upstream can return faster.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2017-04-07 02:34:06 | Re: PATCH: recursive json_populate_record() |
| Previous Message | Michael Paquier | 2017-04-07 02:30:36 | Re: Implementation of SASLprep for SCRAM-SHA-256 |