Re: Vote on SET in aborted transaction - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Vote on SET in aborted transaction
Date
Msg-id 200204231646.g3NGkhh13132@candle.pha.pa.us
Whole thread Raw
In response to Re: Vote on SET in aborted transaction  (Bradley McLean <brad@bradm.net>)
List pgsql-hackers
Bradley McLean wrote:
> * Bruce Momjian (pgman@candle.pha.pa.us) [020423 12:30]:
> >     
> >     1 - All SETs are rolled back in aborted transaction
> >     2 - SETs are ignored after transaction abort
> >     3 - All SETs are honored in aborted transaction
> >     ? - Have SETs vary in behavior depending on variable
> > 
> > Our current behavior is 2.
> > 
> > Please vote and I will tally the results.
> 
> #2, no change in behavior.
> 
> But I base that on the assumption that #1 or #3 involve serious amounts
> of work, and don't see the big benefit.

I don't want to make any big comments during the vote, but I should
mention that #1 is needed by Tom's SET for namespace path, and #1 or #3
is needed to clearly handle query timeouts.

Just thought I would refresh people's memory on how this discussion got
started.

--  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: Bradley McLean
Date:
Subject: Re: Vote on SET in aborted transaction
Next
From: Bruce Momjian
Date:
Subject: Re: Odd(?) RI-trigger behavior