From: | Barry Lind <barry(at)xythos(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | problem with notify/listen |
Date: | 2002-01-15 06:35:29 |
Message-ID: | 3C43CDB1.8020500@xythos.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I have just been looking into a bug report against the jdbc driver and I
found the following behavior that I can't explain.
If I run jdbc with setAutoCommit=true then notifications work as
expected, however if I run with setAutoCommit=false then notifications
are not being sent from the backend to the client.
With autoCommit=false the jdbc driver is sending the following SQL
commands to the server:
begin
select 1
commit;begin;
select 1
commit;begin;
select 1
...
My test code is using the select statement as a means to poll for the
notifications. The only thing that is unusual about this is that the
"commit;begin;" command string is sent to the server as a single query
to be processed.
With autoCommit=true the SQL commands are simply:
select 1
select 1
select 1
...
In this mode the notifications work correctly.
Is there something I am doing wrong, or is this expected behavior for
the server?
thanks,
--Barry
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2002-01-15 06:55:12 | Re: Failure in timestamptz of JDBC of 7.2b4 |
Previous Message | Bruce Momjian | 2002-01-15 06:15:23 | Re: About pg_upgrade |