Re: Patch: raise default for max_wal_segments to 1GB - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Patch: raise default for max_wal_segments to 1GB
Date
Msg-id CAM-w4HN06CA0sj7DbnwzrwA9n2W5757QWFHMK3HO7MhqEE-XtQ@mail.gmail.com
Whole thread Raw
In response to Re: Patch: raise default for max_wal_segments to 1GB  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Mar 3, 2015 at 7:57 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Now, if we were to change the server so that it *refused* settings that
> didn't have a unit, that argument would become moot.  But I'm not going
> to defend the castle against the villagers who will show up if you do
> that.

That might be something we could get away with eventually if we put in
a warning like this for a few years:

WARNING: Using default units of seconds for GUC tcp_keepalives

Though we'll have to deal with the "0 means system default" and "-1
means really really disabled" stuff.

-- 
greg



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: MD5 authentication needs help
Next
From: Robert Haas
Date:
Subject: Re: Normalizing units for postgresql.conf WAS: Patch: raise default for max_wal_segments to 1GB