On 11 January 2017 at 09:51, Fujii Masao <masao.fu...@gmail.com> wrote:
>> 5. recovery.conf parameters are all moved to postgresql.conf, with these >> changes > > In current design of the patch, when recovery parameters are misconfigured > (e.g., set recovery_target_timeline to invalid timeline id) and > the configuration file is reloaded, the startup process emits FATAL error and > the server goes down. I don't think this is fine. Basically even > misconfiguration of the parameters should not cause the server crash. > If invalid settings are supplied, I think that we just should warn them > and ignore those new settings, like current other GUC is. Thought? Thanks for your comments. The specification of the recovery target parameters should be different, IMHO. If the user is performing a recovery and the target of the recovery is incorrectly specified then it is clear that the recovery cannot continue with an imprecisely specified target. So in my understanding we would need to either 1) issue a WARNING and pause recovery 2) issue an ERROR (which becomes FATAL in Startup process) and exit recovery My view would be 2) is the most useful, though I am willing to hear other points and/or go with majority view -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
