On Tue, Aug 18, 2015 at 7:59 AM, Peter Eisentraut <pete...@gmx.net> wrote: > How would we handle decreases at run time? We can prevent >=archive -> > minimal if archiving is running or there are physical replication slots, > and we can prevent logical -> something less if there are logical > replication slots, but AFAICT, we don't have a way to check whether > anyone currently needs level hot_standby.
What do you mean by "prevent"? If the user edits postgresql.conf and reduces the setting, and then reloads the configuration file, they have a right to expect that the changes got applied. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
