Re: Statement.cancel() may cancel queries in the future
От | Bruce Momjian |
---|---|
Тема | Re: Statement.cancel() may cancel queries in the future |
Дата | |
Msg-id | 200309271653.h8RGr1w12330@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: Statement.cancel() may cancel queries in the future (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Statement.cancel() may cancel queries in the future
|
Список | pgsql-jdbc |
Is this something for 7.5? --------------------------------------------------------------------------- Tom Lane wrote: > Oliver Jowett <oliver@opencloud.com> writes: > > On Mon, Sep 15, 2003 at 12:01:47PM -0400, Tom Lane wrote: > >> You could make things a lot closer to > >> synchronous if you wait for the postmaster to drop the connection, > >> instead. That would guarantee that the postmaster has completed > >> executing kill(). I suppose actual delivery of the signal to the > >> backend might not have happened yet, but it's hard to believe that > >> it could be postponed past the backend's next successful execution of > >> recv(). > > > That sounds reasonable. I'll put together a patch to do that. > > It looks like libpq has the same issue, as PQrequestCancel() does not > wait around for the postmaster to drop the connection. Anyone want > to fix that? > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
В списке pgsql-jdbc по дате отправления: