Skip site navigation (1) Skip section navigation (2)

Re: Statement Timeout Message Incorrect

From: elein <elein(at)varlena(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Cc: elein <elein(at)varlena(dot)com>
Subject: Re: Statement Timeout Message Incorrect
Date: 2008-01-24 00:06:19
Message-ID: 20080124000619.GD14970@varlena.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Wed, Jan 23, 2008 at 11:22:06AM -0800, elein wrote:
> Running 8.3RC1
> 
> I have an sql script where one or more create index statements
> raise a statement timeout message. The statement timeout is
> set to 1d.
> 
> The script runs in ~3 hours including the timeout messages.
> 
> The script does this:
> 
> BEGIN;
> create table temp.xxx ...
> insert into temp.xxx ...
> COMMIT;
> create index one on temp.xxx(col1);
> create index one on temp.xxx(col2);
> create index one on temp.xxx(col3);
> create index one on temp.xxx(col4);
> BEGIN;
> drop table public.xxx;
> alter table temp.xxx set schema public;
> COMMIT;
> 
> I have sprinkled the script with show statement_timeout
> and it always returns 1D.
> 
> I suspect either a problem with counting statement time
> or another error is using the statement timeout message.
> 
> Ideas?
> 
> --elein
> elein(at)varlena(dot)com
> 

>>From: Tom Lane <tgl ( at ) sss ( dot ) pgh ( dot ) pa ( dot ) us>
>>To: elein <elein ( at ) varlena ( dot ) com>
>>Subject: Re: Statement Timeout Message Incorrect
>>Date: Wed, 23 Jan 2008 15:52:35 -0500
>>elein <elein ( at ) varlena ( dot ) com> writes:
>>> Running 8.3RC1
>>> I have an sql script where one or more create index statements
>>> raise a statement timeout message. The statement timeout is
>>> set to 1d.
>>
>>Hmmm ... are you using integer timestamps by any chance?
>>It looks to me like TimestampTzPlusMilliseconds() would overflow
>>for such a large timeout.
>>
>>> The script runs in ~3 hours including the timeout messages.
>>
>>If I'm doing the math correctly, 1 day would overflow to about
>>8 minutes in microseconds, so if you're seeing individual statements
>>time out after more than that then there's something else going on.
>>
>>			regards, tom lane
>>

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


We did build with integer timestamps on a 64 bit machine with RC1.

Sorry for the weird format. I'm on the digest and couldn't wait to
reply.

--elein
elein(at)varlena(dot)com

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2008-01-24 00:54:21
Subject: Re: BUG #3898: Postgres autovacuum not respecting pg_autovacuum.enabled = false
Previous:From: Tom LaneDate: 2008-01-23 20:52:35
Subject: Re: Statement Timeout Message Incorrect

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group