From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: rollback ignored until end of transaction block |
Date: | 2005-11-22 23:22:43 |
Message-ID: | 4383A843.7050101@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Kris Jurka wrote:
>
>
> On Wed, 23 Nov 2005, Oliver Jowett wrote:
>
>> I just tried against a server built from HEAD and couldn't reproduce
>> the problem any of the obvious ways.. Think we will need a testcase here.
>>
>
> Another idea that occurred to me that I don't have time to test is that
> processDeadParsedQueries or processDeadPortals doesn't like getting run
> in a stalled transaction.
No errors against CVS HEAD with the CloseStatement/ClosePortal messages
being sent after an error, just before the ROLLBACK:
[...]
<=BE ReadyForQuery(E)
caught expected exception
closing query: select * from pg_proc
simple execute,
handler=org(dot)postgresql(dot)jdbc2(dot)AbstractJdbc2Connection$TransactionCommandHandler(at)6443226,
maxRows=0, fetchSize=0, flags=22
FE=> CloseStatement(S_11)
FE=> ClosePortal(C_12)
FE=> Bind(stmt=S_4,portal=null)
FE=> Execute(portal=null,limit=1)
FE=> Sync
<=BE CloseComplete
<=BE CloseComplete
<=BE BindComplete [null]
<=BE CommandStatus(ROLLBACK)
<=BE ReadyForQuery(I)
rollback was ok
-O
From | Date | Subject | |
---|---|---|---|
Next Message | smitha | 2005-11-23 08:08:45 | Reg : Exception in Postgresql with Java |
Previous Message | Kris Jurka | 2005-11-22 22:57:30 | Re: rollback ignored until end of transaction block |