On 09/06/2013 08:48 PM, Tom Lane wrote: > Andres Freund <and...@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Ü -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
