From: | Christoph Haller <ch(at)rodos(dot)fzk(dot)de> |
---|---|
To: | jasiek(at)klaster(dot)net |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Lock timeout detection in postgres 7.3.1 |
Date: | 2003-02-07 11:39:04 |
Message-ID: | 3E439AD8.7E3C006@rodos.fzk.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
>
> PostgreSQL 7.3 Documentation
> 3.4. Run-time Configuration
> STATEMENT_TIMEOUT (integer)
> Aborts any statement that takes over the specified number of
milliseconds. A value of zero turns off the timer.
> DEADLOCK_TIMEOUT (integer)
> This is the amount of time, in milliseconds, to wait on a lock before
checking to see if there is a deadlock condition
>
>
> In this case I suppose 2 things:
> - table has a lot of records and you should just wait to finish
operation.
> - another query locked the table and it is realy a deadlock
>
Thanks Tomasz for pointing this out.
STATEMENT_TIMEOUT is exactly what I was looking for.
I should have had a look into the 7.3 Doc on my own.
Regards, Christoph
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2003-02-07 11:46:38 | Re: conversi ms-sql7 vs postgresql 7.3 |
Previous Message | Tomasz Myrta | 2003-02-07 10:48:47 | Re: efficient count/join query |