pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: alexondi <alexondi@rambler.ru>
To: pgsql-admin@postgresql.org
Subject: Re: replication_timeout does not seem to be working
Date: Tue, 23 Aug 2011 01:49:42 -0700 (PDT)
Message-ID: <1314089382271-4726014.post@n5.nabble.com> (raw)
In-Reply-To: <CAHGQGwGG=E-abQO6RybxdApg6CFhV_ACykAD_qNivJmez-M9Vg@mail.gmail.com>
References: <1311279255.75976.YahooMailNeo@web120016.mail.ne1.yahoo.com>
	<CAHGQGwH=7eHwbjtnO25T=AH9-D8USov1_ZvrYz7bx+2SRaNWkA@mail.gmail.com>
	<1311351085.55818.YahooMailNeo@web120018.mail.ne1.yahoo.com>
	<CAHGQGwGG=E-abQO6RybxdApg6CFhV_ACykAD_qNivJmez-M9Vg@mail.gmail.com>

>If no reply is returned from the standby in replication_timeout, the master
thinks
>that the connected standby is inactive, and terminates the replication
connection.
>This is useful for the master to detect a standby crash or network outage. 

After that master commit current transaction with "local" synchronous_commit
or rollback?

And why I setup this parameter replication_timeout = 2s and my wal's thread
(on master and server are restarted within 2s)?

--
View this message in context: http://postgresql.1045698.n5.nabble.com/replication-timeout-does-not-seem-to-be-working-tp4620827p47...
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.



view thread (8+ messages)  latest in thread

Message-ID: <1314089382271-4726014.post@n5.nabble.com>
Permalink:  ../1314089382271-4726014.post@n5.nabble.com/
Also on:    postgresql.org/message-id/1314089382271-4726014.post@n5.nabble.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: alexondi@rambler.ru
  Subject: Re: replication_timeout does not seem to be working
  In-Reply-To: <1314089382271-4726014.post@n5.nabble.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox