From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | A J <s5aly(at)yahoo(dot)com> |
Cc: | PG Admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: replication_timeout does not seem to be working |
Date: | 2011-07-25 02:24:35 |
Message-ID: | CAHGQGwGG=E-abQO6RybxdApg6CFhV_ACykAD_qNivJmez-M9Vg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Sat, Jul 23, 2011 at 1:11 AM, A J <s5aly(at)yahoo(dot)com> wrote:
> I am still not clear. Can you explain what replication_timeout parameter
> accomplishes and when ?
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.
> Basically I wish my synchronous write transaction to not wait indefinitely
> when the synchronous standby servers are not available. But rather a
> response returned back to client that write could not be successful, after
> trying for 'n' seconds. How can that be accomplished ?
There is no parameter for that purpose. You would need to implement
something like the monitor daemon which disable synchronous replication
when it detects a standby crash or network outage.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Adarsh Sharma | 2011-07-25 06:38:28 | Restore database after drop command |
Previous Message | Bernhard Rohrer | 2011-07-24 16:21:53 | pg_config |