Re: timeout implementation issues

Hiroshi Inoue <inoue@tpf.co.jp>

From: "Hiroshi Inoue" <Inoue@tpf.co.jp>
To: "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: "Bruce Momjian" <pgman@candle.pha.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-08T17:56:27Z
Lists: pgsql-hackers
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> 
> "Hiroshi Inoue" <Inoue@tpf.co.jp> writes:
> > Sorry for my poor explanation. What I meant is that *Rollback*
> > is to

>> cancel the changes made to SQL-data or schemas

This line is a quote from SQL99 not my creation.
 
> > not to put back the variables which are local to the session.
> 
> Uh, why?  Seems to me you are asserting as a given exactly the
> point that is under debate.  Let me give a counterexample:
> 
> 	BEGIN;
> 	CREATE TEMP TABLE foo;
> 	something-erroneous;
> 	END;
> 
> The creation of the temp table will be rolled back on error, no?

??? TEMP TABLE is a SQL-data not a variable.
I don't think rolling back SETs makes things plain.

regards,
Hiroshi Inoue