| From: | "John Bester" <john(dot)bester(at)snowball(dot)co(dot)za> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #2547: Notifications lost when using JDBC |
| Date: | 2006-07-24 07:23:11 |
| Message-ID: | 200607240723.k6O7NB1e054448@wwwmaster.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 2547
Logged by: John Bester
Email address: john(dot)bester(at)snowball(dot)co(dot)za
PostgreSQL version: 8.1
Operating system: SUSE 10.0
Description: Notifications lost when using JDBC
Details:
I found that if I create a JDBC connection to Postgres and listen for
notifications, it works until I create a new connection. I have not checked
whether notifications are received on the new connection, but even if it did
I would still consider it to be a bug. You should be able to create a
notification listener that works with it's own connection in a seperate
thread without having to know when new connections are made.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schaber | 2006-07-24 07:54:29 | Re: BUG #2543: Performance delay acrros the same day |
| Previous Message | Zdenek Kotala | 2006-07-24 05:45:20 | Re: BUG #2546: PostgreSQL does not have native spinlock support |