Re: A bad behavior under autocommit off mode

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Barry Lind <blind(at)xythos(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Neil Conway <neilc(at)samurai(dot)com>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A bad behavior under autocommit off mode
Date: 2003-03-21 06:10:03
Message-ID: 10397.1048227003@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Barry Lind <blind(at)xythos(dot)com> writes:
> Of these two limitations the first is more significant since users do
> issue 'commit' statements directly sometimes, whereas users would likely
> never change the GUC parameter in their SQL.

Well, we could fix either or both of these in the planned protocol
change. It would be reasonable for the Z message to convey not only
the current transaction state (not in xact/in xact/in failed xact,
I believe are the three interesting states) but also the current
autocommit boolean. So assuming that visibility of state is not the
determining issue, which way do you actually like?

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-03-21 06:12:30 Re: A bad behavior under autocommit off mode
Previous Message Christopher Kings-Lynne 2003-03-21 06:08:27 Re: [HACKERS] Extracting time from timestamp