pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Vladimir Borodin <root@simply.name>
To: Sergey Arlashin <sergeyarl.maillist@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: PostgreSQL 9.3 synchronous replication
Date: Wed, 21 Jan 2015 14:19:05 +0300
Message-ID: <8491EB60-8281-4890-A02D-DC8FF6630D70@simply.name> (raw)
In-Reply-To: <B0A4903C-64EA-4DE1-8676-F1177928F6AB@gmail.com>
References: <B0A4903C-64EA-4DE1-8676-F1177928F6AB@gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>


> 21 янв. 2015 г., в 11:25, Sergey Arlashin <sergeyarl.maillist@gmail.com> написал(а):
> 
> Hi!
> 
> Recently I've found out that synchronous replication just guarantees that the commit has reached the transaction log on the slave. Therefore that doesn't mean the slave has replayed the transaction log and a query against the slave will show the transaction's results.
> 
> So I'm wondering if there is a way to ensure that once a transaction is committed the data is available on the slave and I can get it by executing a query against the slave?

You should set synchronous_commit = on (seems, that right now you have remote_write). See http://www.postgresql.org/docs/current/static/runtime-config-wal.html#GUC-SYNCHRONOUS-COMMIT <http://www.postgresql.org/docs/current/static/runtime-config-wal.html#GUC-SYNCHRONOUS-COMMIT; for more details.

> 
> --
> Best regards,
> Sergey Arlashin
> 
> -- 
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin


--
May the force be with you...
http://simply.name

view thread (7+ messages)  latest in thread

Message-ID: <8491EB60-8281-4890-A02D-DC8FF6630D70@simply.name>
Permalink:  ../8491EB60-8281-4890-A02D-DC8FF6630D70@simply.name/
Also on:    postgresql.org/message-id/8491EB60-8281-4890-A02D-DC8FF6630D70@simply.name

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: root@simply.name, sergeyarl.maillist@gmail.com
  Subject: Re: PostgreSQL 9.3 synchronous replication
  In-Reply-To: <8491EB60-8281-4890-A02D-DC8FF6630D70@simply.name>
  References: <B0A4903C-64EA-4DE1-8676-F1177928F6AB@gmail.com> <8491EB60-8281-4890-A02D-DC8FF6630D70@simply.name>

* 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