Dimitri Fontaine <[email protected]> writes:
> What I have in mind for extensions now that c_v_c is out would be to be
> able to declare any GUC in the control file, with default values, and
> without forcing extension to handle the GUC in its .so â I don't think
> we have to change the code beside removing the c_v_c checks here.
What's the point of that? A value in an extension control file isn't
particularly easily accessible. You'd basically only see it when
loading the extension, and that's a scenario in which the existing
mechanism works just fine. I see no reason to break existing code
here.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
