Re: [RFC] Extend namespace of valid guc names - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: [RFC] Extend namespace of valid guc names
Date
Msg-id 522A32BD.9060000@2ndQuadrant.com
Whole thread Raw
In response to Re: [RFC] Extend namespace of valid guc names  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [RFC] Extend namespace of valid guc names  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 09/06/2013 08:48 PM, Tom Lane wrote:
> Andres Freund <andres@2ndquadrant.com> writes:
>> On 2013-09-06 10:13:23 -0400, Tom Lane wrote:
>>> Well, if you feel an absolute compulsion to make them consistent, I'd
>>> go with making SET disallow creation of variables with names the file
>>> parser wouldn't recognize.  But why is it such a bad thing if SET can
>>> do that?
>> Also, ALTER SYSTEM SET is going to need a similar restriction as well,
>> otherwise the server won't restart although the GUCs pass validation...
> Well, sure, but I would think that ALTER SYSTEM SET should be constrained
> to only set known GUCs, not invent new ones on the fly.
What's the reasoning behind this ?

I was assuming that ALTER SYSTEM SET would allow all GUCs which
do not require restart which includes all "newly invented" ones.

Cheers

-- 
Hannu Krosing
PostgreSQL Consultant
Performance, Scalability and High Availability
2ndQuadrant Nordic OÜ




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [HACKERS] Re: [HACKERS] Is it necessary to rewrite table while increasing the scale of datatype numeric?
Next
From: Jim Nasby
Date:
Subject: Re: [PERFORM] encouraging index-only scans