elein <[EMAIL PROTECTED]> writes:
> So a '1d' (86400 seconds) statement timeout should not be a problem as it
> is not too large.
Indeed. It's a bug that this fails. What's your point?
regards, tom lane
---(end of broadcast)--
> >>From: Tom Lane
> >>To: elein
> >>Subject: Re: Statement Timeout Message Incorrect
> >>Date: Wed, 23 Jan 2008 15:52:35 -0500
> >>elein writes:
> >>> Running 8.3RC1
> >>> I have an sql script where one or more create index statements
> >>> raise a statement timeout message. The statement timeo
elein <[EMAIL PROTECTED]> writes:
> From: Tom Lane
>> 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 tim
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 doe
elein <[EMAIL PROTECTED]> 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()
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
