Horton

Re: timeout implementation issues

Hiroshi Inoue <inoue@tpf.co.jp>

View thread
From: Hiroshi Inoue <Inoue@tpf.co.jp>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>, Thomas Lockhart <lockhart@fourpalms.org>, Peter Eisentraut <peter_e@gmx.net>, Michael Loftis <mloftis@wgops.com>, PostgreSQL Development <pgsql-hackers@postgresql.org>
Date: 2002-04-18T23:53:02Z
Lists: pgsql-hackers 
Tom Lane wrote:
> 
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > I have updated the TODO to:
> >     o Abort all or commit all SET changes made in an aborted transaction
> > I don't think our current behavior is defended by anyone.
> 
> Hiroshi seems to like it ...

Probably I don't love it. Honestly I don't understand
what the new TODO means exactly.
I don't think this is  *all* *should be* or *all
or nothing* kind of thing. If a SET variable has
its reason, it would behave in its own right.

> However, "commit SETs even after an error" is most certainly NOT
> acceptable. 

What I've meant is that SET commands are out of transactional
control and so the word *commit SETs even after* has no meaning
to me. Basically it's a user's responsisbilty to manage the
errors. He only knows what's to do with the errors.

regards,
Hiroshi Inoue
	http://w2422.nsk.ne.jp/~inoue/