From: | Arseny Sher <a(dot)sher(at)postgrespro(dot)ru> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Synchronous logical replication? |
Date: | 2017-07-02 08:27:15 |
Message-ID: | 87a84nnt0c.fsf@ars-thinkpad |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> The reason for this confusion is that synchronous_commit has both a
> local and a remote meaning, and in this case the local meaning on the
> subscriber has an impact on the remote meaning of the publisher.
And another, if I get it right, is that while asynchronous commit makes
server report 'success' faster, it also makes the actual WAL writing to
the disk *slower* in terms of latency, because this action is delayed
for some arbitrary time (well, to be exactly, up to 3*wal_writer_delay
milliseconds). As for synchronous commit, its WAL is written as soon as
possible, though I am not sure which guarantees exist here -- walwriter
is woken up each wal_writer_delay ms, but it seems to write only fully
completed pages under heavy load. Please correct me if I am wrong.
In general, it's clear now, thanks.
--
Arseny Sher
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2017-07-03 09:22:25 | Re: gen_random_uuid security not explicit in documentation |
Previous Message | Peter Eisentraut | 2017-07-02 04:19:44 | Re: Synchronous logical replication? |