Skip site navigation (1) Skip section navigation (2)

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: 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 22:45:14
Message-ID: 200303262245.h2QMjET06851@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > How about sending an INFO or special taged message to the client when
> > there is a GUC change, and have report_changes as a GUC variable that
> > controls it?
> 
> Having such a variable would break the client libraries that need the
> information.  They won't stop needing the info just because some DBA
> thinks it's a good idea to save a few bytes of bandwidth ...

You could configure it so once it is set by the client, only the client
can change it, meaning it doesn't read from postgresql.conf.

-- 
  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

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2003-03-26 22:55:27
Subject: Re: A bad behavior under autocommit off mode
Previous:From: Tom LaneDate: 2003-03-26 22:40:21
Subject: Re: A bad behavior under autocommit off mode

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group