| From: | Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com> |
|---|---|
| To: | Sergey Arlashin <sergeyarl(dot)maillist(at)gmail(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 9.3 synchronous replication |
| Date: | 2015-01-21 18:21:26 |
| Message-ID: | CAJghg4LHOQoOog1dtsk_dZ=PxhSJYkYvenKNQYHQssUcxHyORA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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).
Regards,
--
Matheus de Oliveira
Analista de Banco de Dados
Dextra Sistemas - MPS.Br nível F!
www.dextra.com.br/postgres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2015-01-21 18:42:47 | Re: pg_basebackup bug: base backup is double the size of the database |
| Previous Message | Matheus de Oliveira | 2015-01-21 18:19:47 | Re: pg_basebackup bug: base backup is double the size of the database |