From: Arseny Sher <a.sher@postgrespro.ru>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: Synchronous logical replication?
Date: Sun, 02 Jul 2017 11:27:15 +0300
Message-ID: <87a84nnt0c.fsf@ars-thinkpad> (raw)
In-Reply-To: <7fb9fc7c-72f7-f9ef-3896-9cc7e4fd13b0@2ndquadrant.com>
References: <877ezznax1.fsf@ars-thinkpad>
<7fb9fc7c-72f7-f9ef-3896-9cc7e4fd13b0@2ndquadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
Peter Eisentraut <peter.eisentraut@2ndquadrant.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
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: a.sher@postgrespro.ru, peter.eisentraut@2ndquadrant.com
Subject: Re: Synchronous logical replication?
In-Reply-To: <87a84nnt0c.fsf@ars-thinkpad>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox