Re: timeout implementation issues - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: timeout implementation issues
Date
Msg-id 200204070215.g372FoE02845@candle.pha.pa.us
Whole thread Raw
In response to timeout implementation issues  (Jessica Perry Hekman <jphekman@dynamicdiagrams.com>)
Responses Re: timeout implementation issues  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > We do have on_shmem_exit and on_proc_exit function call queues.  Seems
> > we will need SET to create a queue of function calls containing previous
> > values of variables SEt in multi-statement transactions.  If we execute
> > the queue in last-in-first-out order, the variables will be restored
> > properly.
> 
> That's most certainly the hard way.  I was planning to just make GUC
> save a spare copy of the start-of-transaction value of each variable.

Ewe, I was hoping for something with zero overhead for the non-SET case.
Can we trigger the save for the first SET in the transaction?

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


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: timeout implementation issues
Next
From: Tom Lane
Date:
Subject: Re: timeout implementation issues