On Sat, Dec 24, 2016 at 6:02 AM, David Steele <[email protected]> wrote: > On 12/23/16 10:24 AM, Tom Lane wrote: >> Andres Freund <[email protected]> writes: >>> While it's not a particularly good idea to set it to 1s on a production >>> system, I don't see why we need to prevent that. It's not like 30s is >>> likely to be a good idea either. >> >>> Hence I'd like to set the lower limit to 1s. >> >> OK, but the documentation for it needs some work if you're going to >> do that. It only warns against making the timeout too large, not >> too small. > > +1 for the lower limit and the docs.
I wish we were more loose regarding the limits of some parameters, see for example this recent thread about bgwriter ones: https://www.postgresql.org/message-id/[email protected] So +1 for lowering checkpoint_timeout, lower values are stupid for production systems, but not for developers. -- Michael -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
