| From: | Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: lock timeout patch |
| Date: | 2004-06-28 04:06:00 |
| Message-ID: | 40DF9928.9010805@noanet06.noanet.nttdata.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom,
I guess the transaction cancellation from the client
using PQrequestCancel() is available, but the cancellation
logic must be implemented in the client-application using
signal or thread.
I think detecting such situation on server-side is not
available now, and SQL Server or DB2 have same function.
Tom Lane wrote:
> Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp> writes:
>
>>When a transaction is blocked by another transaction because of
>>waiting a lock, we need a lock timeout in some cases.
>
>
> Isn't there an existing solution for this problem?
>
> regards, tom lane
>
--
NAGAYASU Satoshi <nagayasus(at)nttdata(dot)co(dot)jp>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-06-28 04:18:44 | Re: lock timeout patch |
| Previous Message | Tom Lane | 2004-06-28 03:53:48 | Re: lock timeout patch |