| From: | Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | lock timeout patch |
| Date: | 2004-06-28 03:28:13 |
| Message-ID: | 40DF904D.4040208@noanet06.noanet.nttdata.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello all,
I've created a lock timeout patch and it's attached.
When a transaction is blocked by another transaction because of
waiting a lock, we need a lock timeout in some cases.
Using this patch, the lock timeout is enabled with
'lock_timeout = xxxx' directive in postgresql.conf,
and if a timeout is occured, an error code (40P02)
will be returned and a client application can detect it using
JDBC: SQLException.getSQLState()
C: PQresultErrorField()
I know my code need to be cleaned up,
but any comments about this patch?
--
NAGAYASU Satoshi <nagayasus(at)nttdata(dot)co(dot)jp>
| Attachment | Content-Type | Size |
|---|---|---|
| locktimeout.diff | text/plain | 23.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-06-28 03:52:52 | Re: Fixing pg_dump |
| Previous Message | Christopher Kings-Lynne | 2004-06-28 03:27:15 | Re: Fixing pg_dump |