Re: Could synchronous streaming replication really degrade the performance of the primary? - Mailing list pgsql-performance

From Claudio Freire
Subject Re: Could synchronous streaming replication really degrade the performance of the primary?
Date
Msg-id CAGTBQpYXUeWm1O+rc4NCZxeFB8Oxi8LJuSme-As9b4m6iU0Nbg@mail.gmail.com
Whole thread Raw
In response to Re: Could synchronous streaming replication really degrade the performance of the primary?  (Robert Klemme <shortcutter@googlemail.com>)
Responses Re: Could synchronous streaming replication really degrade the performance of the primary?  (Robert Klemme <shortcutter@googlemail.com>)
List pgsql-performance
On Wed, May 9, 2012 at 12:41 PM, Robert Klemme
<shortcutter@googlemail.com> wrote:
> I am not sure whether the replicant can be triggered to commit to disk
> before the commit to disk on the master has succeeded; if that was the
> case there would be true serialization => 50%.
>
> This sounds like it could actually be the case (note the "after it commits"):
> "When synchronous replication is requested the transaction will wait
> after it commits until it receives confirmation that the transfer has
> been successful."
> http://wiki.postgresql.org/wiki/Synchronous_replication

That should only happen for very short transactions.
IIRC, WAL records can be sent to the slaves before the transaction in
the master commits, so bigger transactions would see higher
parallelism.

pgsql-performance by date:

Previous
From: Robert Klemme
Date:
Subject: Re: Could synchronous streaming replication really degrade the performance of the primary?
Next
From: Robert Klemme
Date:
Subject: Re: Could synchronous streaming replication really degrade the performance of the primary?