Re: New trigger option of pg_standby - Mailing list pgsql-hackers

From Guillaume Smet
Subject Re: New trigger option of pg_standby
Date
Msg-id 1d4e0c10903270021s4c7bbfccxee1c8b731302988d@mail.gmail.com
Whole thread Raw
In response to Re: New trigger option of pg_standby  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Fri, Mar 27, 2009 at 3:38 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> OK, I'll change the patch as Simon suggested; removing -t and adding
> two new options: -f = fast failover (existing behavior), -p patient failover.
> Also I'll default the patient failover, so it's performed when the signal
> (SIGINT or SIGUSR1) is received.

I'm wondering if we should consider backpatching this one. Even if the
feature works as advertised in the documentation.

It's a very surprising behaviour and I'm pretty sure someone will
shoot himself in the foot with it, if not already done.

Considering backpatching might change the way we want to fix it.

-- 
Guillaume


pgsql-hackers by date:

Previous
From: Guillaume Smet
Date:
Subject: Re: New trigger option of pg_standby
Next
From: Guillaume Smet
Date:
Subject: Re: display previous query string of idle-in-transaction