Re: pgsql: Raise maximum value of several timeout parameters

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Raise maximum value of several timeout parameters
Date: 2011-03-18 23:00:14
Message-ID: 4D83E3FE.3010809@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 03/17/2011 02:25 PM, Peter Eisentraut wrote:
> Raise maximum value of several timeout parameters
>
> The maximum value of deadlock_timeout, max_standby_archive_delay,
> max_standby_streaming_delay, log_min_duration_statement, and
> log_autovacuum_min_duration was INT_MAX/1000 milliseconds, which is
> about 35min, which is too short for some practical uses. Raise the
> maximum value to INT_MAX; the code that uses the parameters already
> supports that just fine.
>
>

Did we not intend to backpatch this? The max_standby_*_delay settings
are particularly worrisome to me, and ISTM there's a good case for
calling these just bugs. Surely nobody is relying on the maximum value
being 35 minutes.

cheers

andrew

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2011-03-18 23:18:34 pgsql: Document that the timestamp returned by pg_last_xact_replay_time
Previous Message Andrew Dunstan 2011-03-18 22:56:13 Re: pgsql: Document the all-balls IPv6 address.