| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Remove lower limit on checkpoint_timeout? |
| Date: | 2016-12-23 21:02:12 |
| Message-ID: | e658d522-a792-e08f-73d1-d4d457237dea@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/23/16 10:24 AM, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> 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.
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2016-12-23 21:54:14 | Re: Improvements in psql hooks for variables |
| Previous Message | Tom Lane | 2016-12-23 20:44:12 | Re: Incautious handling of overlength identifiers |