| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Unnecessary limit on max_standby_streaming_delay |
| Date: | 2011-03-11 03:20:15 |
| Message-ID: | 201103110320.p2B3KFn13624@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut wrote:
> On fre, 2010-12-17 at 12:57 +0100, Magnus Hagander wrote:
> > The limit on max_standby_streaming_delay is currently 35 minutes
> > (around) - or you have to set it to unlimited. This is because the GUC
> > is limited to MAX_INT/1000, unit milliseconds.
> >
> > Is there a reason for the /1000, or is it just an oversight thinking
> > the unit was in seconds?
>
> Yeah, I actually noticed this week that log_min_duration_statement is
> limited to the same 35 minutes for the same reason. Might be good to
> address that, too. Note that statement_timeout does not have that
> limit.
Added to TODO:
Increase maximum values for max_standby_streaming_delay and
log_min_duration_statement
* http://archives.postgresql.org/pgsql-hackers/2010-12/msg01517.php
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-03-11 03:28:01 | Re: psql expanded auto |
| Previous Message | Robert Haas | 2011-03-11 03:18:30 | Re: function(contants) evaluated for every row |