On Sun, Jan 12, 2014 at 8:48 AM, Josh Berkus <j...@agliodbs.com> wrote: > On 01/10/2014 06:27 PM, Bruce Momjian wrote: >> How would that work? Would it be a tool in contrib? There already is a >> timeout, so if a tool checked more frequently than the timeout, it >> should work. The durable notification of the admin would happen in the >> tool, right? > > Well, you know what tool *I'm* planning to use. > > Thing is, when we talk about auto-degrade, we need to determine things > like "Is the replica down or is this just a network blip"? and take > action according to the user's desired configuration. This is not > something, realistically, that we can do on a single request. Whereas > it would be fairly simple for an external monitoring utility to do: > > 1. decide replica is offline for the duration (several poll attempts > have failed) > > 2. Send ALTER SYSTEM SET to the master and change/disable the > synch_replicas.
Will it possible in current mechanism, because presently master will not accept any new command when the sync replica is not available? Or is there something else also which needs to be done along with above 2 points to make it possible. With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers