| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com> |
| Cc: | Sergey Arlashin <sergeyarl(dot)maillist(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 9.3 synchronous replication |
| Date: | 2015-01-22 04:15:46 |
| Message-ID: | 20150122041546.GA27757@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Jan 21, 2015 at 04:21:26PM -0200, Matheus de Oliveira wrote:
>
> On Wed, Jan 21, 2015 at 1:21 PM, Sergey Arlashin <sergeyarl(dot)maillist(at)gmail(dot)com>
> wrote:
>
> Yes, I understand this. But I was wondering whether it is possible to
> somehow force this procedure. Or wait until xlog is applied on slave and
> only then consider the transaction committed.
>
>
> You'd have to do it somehow in your application. AFAICT, PostgreSQL does not
> provide any way to that in current versions (might be done in future releases).
The problem with forcing the WAL to be replayed is that it might cause
many existing transactions to be canceled due to their snapshots
becoming invalid.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2015-01-22 04:18:17 | Re: pg_basebackup bug: base backup is double the size of the database |
| Previous Message | Bruce Momjian | 2015-01-22 03:46:17 | Re: Back to my pg_upgrade stoppage problem |