Dear PostgreSQL people,
Sorry for jumping into this conversation in the middle.
Autocommit is very important, as appservers may turn it on or off at
will in order to support EJB transactions (being able to set them up, roll
them back, commit them, etc. by using the JDBC API). If it is broken, then
all EJB apps using PostgreSQL may be broken also. ...This frightens me a
little. Could somebody please explain?
Sincerely,
Daryl.
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Monday, September 09, 2002 2:54 PM
> To: Bruce Momjian
> Cc: Barry Lind; pgsql-jdbc@postgresql.org;
> pgsql-hackers@postgresql.org
> Subject: Re: [JDBC] [HACKERS] problem with new autocommit config
> parameter and jdbc
>
>
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Barry Lind wrote:
> >> How should client interfaces handle this new autocommit
> feature? Is it
> >> best to just issue a set at the beginning of the
> connection to ensure
> >> that it is always on?
>
> > Yes, I thought that was the best fix for apps that can't deal with
> > autocommit being off.
>
> If autocommit=off really seriously breaks JDBC then I don't think a
> simple SET command at the start of a session is going to do that much
> to improve robustness. What if the user issues another SET to turn it
> on?
>
> I'd suggest just documenting that it is broken and you can't use it,
> until such time as you can get it fixed. Band-aids that only
> partially
> cover the problem don't seem worth the effort to me.
>
> In general I think that autocommit=off is probably going to be very
> poorly supported in the 7.3 release. We can document it as being
> "work in progress, use at your own risk".
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>