Re: [HACKERS] Proposal for new SET variables for optimizer costs - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Proposal for new SET variables for optimizer costs
Date
Msg-id 16041.949793483@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Proposal for new SET variables for optimizer costs  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: [HACKERS] Proposal for new SET variables for optimizer costs
List pgsql-hackers
Philip Warner <pjw@rhyme.com.au> writes:
> Any chance of prefixing the 'set' variable names with 'PG_' or 'PG_OPT_' or
> something similar? Or doing something else to differentiate them from
> user-declared SQL variables?

I see no need to do that, since the *only* place these names exist is
in the SET command (and its friends SHOW and RESET), and SET exists only
to set system control variables.  There are no user-declared SQL
variables.

The names are quite long and underscore-filled enough without adding
unnecessary prefixes, IMHO ;-)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Philip Warner
Date:
Subject: Re: [HACKERS] Proposal for new SET variables for optimizer costs
Next
From: Chris
Date:
Subject: Re: Status of inheritance-changing patch