| 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: | 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-27 04:50:59 |
| Message-ID: | 200303270450.h2R4oxW24311@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:
> > 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...
My idea of using a string is that it is easier to pass up to application
that use libpq, like psql. Psql need to know about client encoding
changes.
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas T. Thai | 2003-03-27 04:51:19 | Re: BUG: Vacuum Analyze - datumGetSize: Invalid typLen 0 |
| Previous Message | Thomas T. Thai | 2003-03-27 04:35:25 | Re: BUG: Vacuum Analyze - datumGetSize: Invalid typLen 0 |