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.maillist@xxxxxxxxx> > 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@xxxxxxxxxx> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
