On 15 March 2015 at 14:16, Andres Freund <and...@2ndquadrant.com> wrote:
> Personally I think we just should change the default to 'shutdown' for > all cases. That makes documentation and behaviour less surprising. And > makes experimenting less dangerous, since you can just start again. We need to look at the specific situation, not make a generic decision. If hot_standby = off, we are unable to unpause, once paused. Changing the default doesn't alter that problem. We have two choices: 1) override to a sensible setting, 2) throw an error. (2) sounds clean at first but we must look deeper. We know that the *only* possible other setting is 'shutdown', so it seems more user friendly to do the thing we *know* they want (1), rather than pretend that we don't. (1) is completely predictable and not at all surprising. Add a LOG message if you wish, but don't throw an error. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, RemoteDBA, 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
