On Thu, Feb 5, 2015 at 4:42 PM, Heikki Linnakangas <hlinnakan...@vmware.com> wrote: > Actually, perhaps we should have a boolean setting that just implies > min=max, instead of having a configurable minimum?. That would cover all of > those reasons pretty well. So we would have a "max_wal_size" setting, and a > boolean "preallocate_all_wal = on | off". Would anyone care for the > flexibility of setting a minimum that's different from the maximum?
I like the way you have it now better. If we knew for certain that there were no advantage in configuring a value between 0 and the maximum, that would be one thing, but we don't and can't know that. -- 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
