Re: Statement Timeout Message Incorrect

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: elein <elein(at)varlena(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Statement Timeout Message Incorrect
Date: 2008-01-24 01:09:42
Message-ID: 28798.1201136982@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

elein <elein(at)varlena(dot)com> writes:
> From: Tom Lane <tgl ( at ) sss ( dot ) pgh ( dot ) pa ( dot ) us>
>> Hmmm ... are you using integer timestamps by any chance?
>> It looks to me like TimestampTzPlusMilliseconds() would overflow
>> for such a large timeout.

> Is this a bug or should there be documentation that tells us the max
> of statement timeout should be (what?)

It's a bug. You're supposed to get an error if you set the value too
large:

regression=# set statement_timeout TO '30d';
ERROR: invalid value for parameter "statement_timeout": "30d"
HINT: Value exceeds integer range.

Patch is in CVS already, please check if it fixes it for you.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2008-01-24 03:01:13 Re: BUG #3898: Postgres autovacuum not respecting pg_autovacuum.enabled = false
Previous Message Tom Lane 2008-01-24 00:54:21 Re: BUG #3898: Postgres autovacuum not respecting pg_autovacuum.enabled = false