Skip site navigation (1) Skip section navigation (2)

Re: When running with autocommit false only the first BEGIN

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: pg(at)fastcrypt(dot)com, Barry Lind <blind(at)xythos(dot)com>,pgsql-jdbc(at)postgresql(dot)org
Subject: Re: When running with autocommit false only the first BEGIN
Date: 2004-11-23 15:48:09
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
Oliver Jowett <oliver(at)opencloud(dot)com> writes:
> Dave Cramer wrote:
>> That certainly doesn't seem acceptable. As Barry points out people will 
>> really be in the dark when their code doesn't work.

> There's nothing much the driver can do about it other than not using the 
> new features of V3. This needs a server-side fix.

Step right up ;-)

> See 
> for past discussion. I looked at fixing it briefly but didn't have time 
> to put together a patch.

I think the code changes would be minimal, the hard part is agreeing on
desirable behavior.  From the point of view of "logging what actually
happened", logging at Execute would make sense; but as Oliver noted in
the above thread, that would lose the ability to log statements with
parse errors, which is not good either.  And what about being able to
see the actual parameters sent in Bind?

Also it would be good to think about a saner behavior for logging
statements executed via SPI (ie plpgsql functions) --- we've been living
with essentially these same problems for years there, and no one's very
happy about it.

			regards, tom lane

In response to

pgsql-jdbc by date

Next:From: Hunter HillegasDate: 2004-11-23 23:56:59
Subject: Copying into Unicode - Correcting Errors
Previous:From: Vadim NasardinovDate: 2004-11-23 15:15:29
Subject: Re: Can't throw the dreaded 'idle in transaction' - need help!

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group