| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Joao Rui Leal <joao(dot)leal(at)ciengis(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Deadlock while using getNotifications() and Statement.executeQuery() |
| Date: | 2008-04-01 07:22:24 |
| Message-ID: | 47F1E2B0.3010705@ejurka.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Joao Rui Leal wrote:
> On Tuesday 25 March 2008, Kris Jurka wrote:
>> Still that's not a real clean/understandable design. Perhaps instead
>> processNotifies() should be added to the public QueryExecutor interface
>> and then AbstractJdbc2Connection can call processNotifies itself so that
>> fetching notifications from protoConnection doesn't require any
>> interaction with the QueryExecutor.
>
> I agree.
>
I've applied the attached patch to CVS back to the 8.1 driver. The 8.0
driver does not have this problem because it doesn't allow notification
retrieval without executing a query.
Thanks for the report and diagnosis.
Kris Jurka
| Attachment | Content-Type | Size |
|---|---|---|
| syncnot.patch | text/x-patch | 3.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2008-04-01 08:03:34 | Re: CallableStatement and getUpdateCount |
| Previous Message | Guillaume Smet | 2008-04-01 06:52:55 | Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work |