Re: timeout implementation issues

Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Ewe, I was hoping for something with zero overhead for the non-SET case.
> 
> Well, a function call and immediate return if no SET has been executed
> in the current xact seems low enough overhead to me.  We'll just keep
> a flag showing whether there's anything to do.

Oh, I thought you were going to save all the GUC variables on
transaction start.  I now assume you are going to have one field per
variable for the pre-xact value.  That is fine.

--  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,
Pennsylvania19026