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: Peter Eisentraut <peter_e(at)gmx(dot)net>, 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-26 23:08:52
Message-ID: 7380.1048720132@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:
> My basic idea was using INFO-like message to send the SET change
> information.

Well, that's not really materially different from what I was proposing,
except that I was thinking of a format in which the variable name and
value are separate fields of a protocol message. If we send it out
as an INFO-message-like thingy then the client library has to parse
that string...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Brown 2003-03-26 23:42:24 Re: A bad behavior under autocommit off mode
Previous Message Bruce Momjian 2003-03-26 22:56:57 Re: A bad behavior under autocommit off mode