Re: A bad behavior under autocommit off mode

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Barry Lind <blind(at)xythos(dot)com>, 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-22 18:15:03
Message-ID: 200303221815.h2MIF3N20221@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I realize the transaction status varies from query to query, so that can
> > be hard-wired into the protocol --- but the other ones seem mostly to be
> > cases where you don't want the user changing something behind the back
> > of the interface.
>
> Right.
>
> > If we give the interface more control, we don't have
> > to report back the SET status.
>
> That seems to be going in the wrong direction, though, in terms of
> flexibility.

I was just trying to avoid the interface complexity _if_ preventing SET
was all that was needed.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-03-22 18:16:42 Re: PQescapeBytea on Win32
Previous Message Tom Lane 2003-03-22 18:12:41 Re: A bad behavior under autocommit off mode