On 2/3/15 11:00 AM, Robert Haas wrote: > Crazy ideas: Could we make wal_level something other than > PGC_POSTMASTER? PGC_SIGHUP would be nice... Could we, maybe, even > make it a derived value rather than one that is explicitly configured? > Like, if you set max_wal_senders>0, you automatically get > wal_level=hot_standby? If you register a logical replication slot, > you automatically get wal_level=logical?
We could probably make wal_level changeable at run-time if we somehow recorded to the point at which it was changed, as you describe later (or even brute-force it by forcing a checkpoint every time it is changed, which is not worse than what we require now (or even just write out a warning that the setting is not effective until after a checkpoint)). But that still leaves max_wal_senders (and arguably max_replication_slots) requiring a restart before replication can start. I don't see a great plan for those on the horizon. To me, the restart requirement is the killer. That there are so many interwoven settings isn't great either, but there will always be more options, and all we can do is manage it. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
