Re: timeout implementation issues

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Jessica Perry Hekman" <jphekman(at)dynamicdiagrams(dot)com>, "Jan Wieck" <janwieck(at)yahoo(dot)com>, "Barry Lind" <barry(at)xythos(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: timeout implementation issues
Date: 2002-04-08 17:56:27
Message-ID: EKEJJICOHDIEMGPNIFIJAELJHGAA.Inoue@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>
> "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-04-08 18:05:03 Re: timeout implementation issues
Previous Message Hiroshi Inoue 2002-04-08 17:56:08 Re: timeout implementation issues