Re: timeout implementation issues

Bruce Momjian <pgman@candle.pha.pa.us>

From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Hiroshi Inoue <Inoue@tpf.co.jp>
Cc: Peter Eisentraut <peter_e@gmx.net>, Michael Loftis <mloftis@wgops.com>, PostgreSQL Development <pgsql-hackers@postgresql.org>
Date: 2002-04-10T00:13:21Z
Lists: pgsql-hackers
Hiroshi Inoue wrote:
> Hiroshi Inoue wrote:
> > 
> > Bruce Momjian wrote:
> > >
> > > OK, we have three possibilities:
> > >
> > >         o  All SETs are honored in an aborted transaction
> > >         o  No SETs are honored in an aborted transaction
> > >         o  Some SETs are honored in an aborted transaction (current)
> > >
> > > I think the problem is our current behavior.  I don't think anyone can
> > > say our it is correct (only honor SET before the transaction reaches
> > > abort state).  Whether we want the first or second is the issue, I think.
> > 
> > I think the current state is not that bad at least
> > is better than the first.
> 
> Oops does the first mean rolling back the variables on abort ?
> If so I made a mistake. The current is better than the second.

The second means all SET's are rolled back on abort.
 
-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026