Re: Specific names for plpgsql variable-resolution control options? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Specific names for plpgsql variable-resolution control options?
Date
Msg-id 11745.1257555462@sss.pgh.pa.us
Whole thread Raw
In response to Re: Specific names for plpgsql variable-resolution control options?  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: Specific names for plpgsql variable-resolution control options?
List pgsql-hackers
"David E. Wheeler" <david@kineticode.com> writes:
> On Nov 6, 2009, at 12:21 PM, Tom Lane wrote:
>> What we did not have was any concrete suggestions for the name or
>> values of the GUC, nor for the exact per-function syntax beyond the
>> thought that it could look something like the existing '#option dump'
>> modifier.

> plpgsql_variable_conflict = fatal | oracle-compat | pg-compat

plpgsql_variable_conflict is all right, but I think we should avoid
using Oracle's trademarked name in the setting names.  I was envisioning
setting names related to "variable first" or "column first" or something
in that line.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled
Next
From: Tom Lane
Date:
Subject: Re: Quoting oddities when defining operators in postgres 8.3