Re: [INTERFACES] Roadmap for FE/BE protocol redesign

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Barry Lind <blind(at)xythos(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign
Date: 2003-03-22 01:53:09
Message-ID: 200303220153.h2M1r9X01499@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces

Barry Lind wrote:
>
>
> Bruce Momjian wrote:
> > I was thinking if we had a SET PERMANENT that couldn't be changed,
> > interfaces that want to control variables could set them perminantly,
> > and others could let users control it.
>
> SET PERMANENT only works for those variables that can only have one
> value for a given client protocol (for example datestyle in jdbc).
> Whereas autocommit needs to be changeable by the jdbc driver since the
> jdbc spec allows the user to call an API method to change the setting.

Oh, good point.

>
> >
> > Actually, if we reported change to the client, the interface could
> > override any change the user made --- just an idea.
>
> Reporting the change to the client seems sufficient for the client to
> take whatever actions are necessary.

--
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 01:54:02 Re: installcheck failure
Previous Message Bruce Momjian 2003-03-22 01:48:17 Re: A bad behavior under autocommit off mode

Browse pgsql-interfaces by date

  From Date Subject
Next Message Bruce Momjian 2003-03-22 01:58:10 Re: plpython problem.
Previous Message Barry Lind 2003-03-21 23:28:03 Re: [INTERFACES] Roadmap for FE/BE protocol redesign