| 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:37:02 |
| Message-ID: | 40DFA06E.5010206@noanet06.noanet.nttdata.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
statement_timeout terminates large sort or scan
even if it is running, doesn't it?
statement_timeout doesn't care that
the process is waiting a lock or running.
I don't want to terminate a running query.
So a lock waiting backend shold be killed.
Tom Lane wrote:
> Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp> writes:
>
>>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.
>
>
> Actually I think the recommended solution involves using statement_timeout.
>
> regards, tom lane
>
--
NAGAYASU Satoshi <nagayasus(at)nttdata(dot)co(dot)jp>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-06-28 05:02:44 | Re: lock timeout patch |
| Previous Message | Tom Lane | 2004-06-28 04:18:44 | Re: lock timeout patch |