Re: New trigger option of pg_standby
От | Fujii Masao |
---|---|
Тема | Re: New trigger option of pg_standby |
Дата | |
Msg-id | 3f0b79eb0903261938l15a6a8b8v5a7f8dec2c795cef@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: New trigger option of pg_standby (Guillaume Smet <guillaume.smet@gmail.com>) |
Ответы |
Re: New trigger option of pg_standby
Re: New trigger option of pg_standby |
Список | pgsql-hackers |
Hi, On Thu, Mar 26, 2009 at 8:54 PM, Guillaume Smet <guillaume.smet@gmail.com> wrote: > Hi Simon. > > On Thu, Mar 26, 2009 at 11:50 AM, Simon Riggs <simon@2ndquadrant.com> wrote: >> Earlier, we discussed having a single trigger file that contains an >> option rather than two distinct trigger files. That design is better >> because it allows the user to choose at failover time, rather than >> making a binding decision at config time. That solution would be the >> ideal one, IMHO, because it gives user more choice - and would allow us >> to keep the -t option meaningfully. In that case the default should be >> patience. > > Or you can define both files in your command line to have the choice. Personally I like this. > I like the idea of removing -t and adding 2 new options so that people > are warned about the intended behavior. 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. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: