Re: timeout implementation issues

Hiroshi Inoue <inoue@tpf.co.jp>

From: "Hiroshi Inoue" <Inoue@tpf.co.jp>
To: "Bruce Momjian" <pgman@candle.pha.pa.us>
Cc: "Tom Lane" <tgl@sss.pgh.pa.us>, "Peter Eisentraut" <peter_e@gmx.net>, "Jessica Perry Hekman" <jphekman@dynamicdiagrams.com>, "Jan Wieck" <janwieck@yahoo.com>, "Barry Lind" <barry@xythos.com>, <pgsql-hackers@postgresql.org>
Date: 2002-04-08T16:32:52Z
Lists: pgsql-hackers
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
>
> Hiroshi Inoue wrote:
> > > >
> > > > I feel we should just do it.  Yeah, there might be some corner cases
> > > > where it's not the ideal behavior; but you haven't convinced me that
> > > > there are more cases where it's bad than where it's good. You sure
> > > > haven't convinced me that it's worth making SET's behavior
> > > > nigh-unpredictable-without-a-manual, which is what
> per-variable behavior
> > > > would be.
> > >
> > > I am with Tom on this one.  (Nice to see he is now arguing on
> my side.)
> >
> > I vote against you. If a variable is local to the session, you
> > can change it as you like without bothering any other user(session).
> > Automatic resetting of the varibales is rather confusing to me.
>
> I don't see how this relates to other users.  All SET commands that can
> be changed in psql are per backend, as far as I remember.

Sorry for my poor explanation. What I meant is that *Rollback*
is to cancel the changes made to SQL-data or schemas
not to put back the variables which are local to the session.

regards,
Hiroshi Inoue