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

From Thomas Lockhart
Subject Re: Vote totals for SET in aborted transaction
Date
Msg-id 3CCD6C06.64C2A73@fourpalms.org
Whole thread Raw
In response to Re: Vote totals for SET in aborted transaction  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Vote totals for SET in aborted transaction  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
...
> Agreed, very non-intuitive.  And can you imagine how many applications
> we would break.

What is non-intuitive about it? What it *does* do is free the programmer
from worrying about side effects which *do* break applications.

Rather than dismissing this out of hand, try to look at what it *does*
enable. It allows developers to tune specific queries without having to
restore values afterwards. Values or settings which may change from
version to version, so end up embedding time bombs into applications.

And the number of current applications "broken"? None, as a starting
point ;)
                 - Thomas


pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: Vote totals for SET in aborted transaction
Next
From: Tom Lane
Date:
Subject: Re: Vote totals for SET in aborted transaction