Re: PostgreSQL 9.3 synchronous replication
| От | Vladimir Borodin |
|---|---|
| Тема | Re: PostgreSQL 9.3 synchronous replication |
| Дата | |
| Msg-id | 8491EB60-8281-4890-A02D-DC8FF6630D70@simply.name обсуждение исходный текст |
| Ответ на | PostgreSQL 9.3 synchronous replication (Sergey Arlashin <sergeyarl.maillist@gmail.com>) |
| Ответы |
Re: PostgreSQL 9.3 synchronous replication
|
| Список | pgsql-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 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
В списке pgsql-admin по дате отправления: