Re: A bad behavior under autocommit off mode

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(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:12:41
Message-ID: 1845.1048356761@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-03-22 18:15:03 Re: A bad behavior under autocommit off mode
Previous Message Bruce Momjian 2003-03-22 17:48:25 Re: A bad behavior under autocommit off mode