Re: SET LOCAL again - Mailing list pgsql-hackers

From Tom Lane
Subject Re: SET LOCAL again
Date
Msg-id 5979.1028047497@sss.pgh.pa.us
Whole thread Raw
In response to Re: SET LOCAL again  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: SET LOCAL again  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> Tom Lane writes:
> As an alternative syntax I can suggest
>> 
> SET name TO value [ ON COMMIT RESET ];
>> 
>> Ugh.  Why can't we stick with SET LOCAL?

> SET LOCAL is already used for something else in the SQL standard.  Not
> sure if we'll ever implement that, but it's something to be concerned
> about.

Actually, it looks to me like the spec's SET LOCAL has a compatible
interpretation: it only affects the current transaction.

My main gripe with "ON COMMIT RESET" is that it's a misleading
description of what will happen --- RESETting a variable is quite
different from allowing it to revert to the pre-transaction state.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: contrib/ltree for 7.2 or 7.3 ?
Next
From: Andrew Sullivan
Date:
Subject: Re: WAL file location