Re: Vote totals for SET in aborted transaction

From: Jan Wieck <janwieck(at)yahoo(dot)com>
To: Sander Steffann <sander(at)steffann(dot)nl>
Cc: Jan Wieck <janwieck(at)yahoo(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Vote totals for SET in aborted transaction
Date: 2002-04-25 14:18:26
Message-ID: 200204251418.g3PEIUt29022@saturn.janwieck.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sander Steffann wrote:
> > What about a SET variable that controls the behaviour of
> > SET variables :-)
>
> Or two commands for the same thing:
> - a SET command that behaves as it does now
> - a TSET command that is transaction-aware
>
> Ouch... :-)
> Sander

Naw, that's far too easy. I got it now, a

CONFIGURE variable ON ROLLBACK <action>

action: SET DEFAULT (read again from .conf)
| SET 'value' (might fail, fallback to .conf)
| NO ACTION (ignore rollback)
| ROLLBACK (return to value before transaction)

Also, we should make all these settings DB dependant and be
able to specify the configure settings in the .conf file, so
that two databases running under the same postmaster bahave
completely different, just to make the confusion perfect for
every client.

And for everyone who didn't get it, this was sarcasm!

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Scherbaum 2002-04-25 14:34:26 Re: new food for the contrib/ directory
Previous Message Tom Lane 2002-04-25 13:54:32 Re: Sequential Scan Read-Ahead