Horton

Re: timeout implementation issues

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hiroshi Inoue <Inoue@tpf.co.jp>
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:56:13Z
Lists: pgsql-hackers 
Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> 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.

Well, we could provide some kind of escape hatch to let the behavior
vary from one variable to the next.  But can you give any specific
examples?  Which SET variables should not roll back on error?

			regards, tom lane