Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YE9BU-0000kn-4L for pgsql-admin@arkaria.postgresql.org; Thu, 22 Jan 2015 04:15:56 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YE9BS-0003tx-TO for pgsql-admin@arkaria.postgresql.org; Thu, 22 Jan 2015 04:15:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YE9BS-0003tr-4h for pgsql-admin@postgresql.org; Thu, 22 Jan 2015 04:15:54 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YE9BN-0002QS-4b for pgsql-admin@postgresql.org; Thu, 22 Jan 2015 04:15:52 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1YE9BK-0008Ab-7V; Wed, 21 Jan 2015 23:15:46 -0500 Date: Wed, 21 Jan 2015 23:15:46 -0500 From: Bruce Momjian To: Matheus de Oliveira Cc: Sergey Arlashin , pgsql-admin Subject: Re: PostgreSQL 9.3 synchronous replication Message-ID: <20150122041546.GA27757@momjian.us> References: <4D515075-C030-4E13-80E8-42C3F6A7FC80@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org 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 > 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 http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin