Re: pgsql: Integrate recovery.conf into postgresql.conf
От | Alvaro Herrera |
---|---|
Тема | Re: pgsql: Integrate recovery.conf into postgresql.conf |
Дата | |
Msg-id | 20181126180943.fdj3dkajqtqifekb@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: pgsql: Integrate recovery.conf into postgresql.conf (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: pgsql: Integrate recovery.conf into postgresql.conf
|
Список | pgsql-hackers |
On 2018-Nov-26, Stephen Frost wrote: > I would think we'd have the different GUCs and then the check functions > would only validate that they're valid inputs and then when we get to > the point where we're starting to do recovery we check and make sure > we've been given a sane overall configuration- which means that only > *one* is set, and it matches the recovery target requested. I don't quite understand why it isn't sensible to specify more than one and just stop recovery (or whatever) when at least one of them becomes true. Maybe I want to terminate just before commit of transaction 12345, but no later than 2018-11-11 12:47 in any case. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: