On Thu, 2010-04-29 at 14:55 +0300, Heikki Linnakangas wrote:
> I'd like to scaremonger
Seems so.
recovery_connections was on by default and unanimous agreement until
recently and I don't want to change that now, just because a change
somewhere else appears to be forcing that but need not be so. It was
sensible to add a switch to turn HS off, but it should not be the
default, especially not one that requires a restart to enable a high
availability feature.
That is important in a feature that takes a while to "kick-in" and so
the user may patiently wait for it to come up and it never does.
I have no wish to repeat the situation that PostgreSQL requires a
restart to enable a feature, while other forks retain the ability to
enable the parameter without restart, as occurs with archive_mode, IIRC.
Perhaps we should not re-think wal_level if we've just moved the
parameter problem somewhere else?
-- Simon Riggs www.2ndQuadrant.com
