Re: GUC vs variable.c (was Patches applied...)

Thomas Lockhart <thomas@fourpalms.org> writes:
>> However, it seems to me way past time that we did what needs to be done
>> with variable.c --- ie, get rid of it.  All these special-cased
>> variables should be folded into GUC.

> Or in some cases into pg_database? We might want some of this to travel
> as database-specific properties adjustable using SQL or SET syntax.

Ah, but we *have* that ability right now; see Peter's recent changes
to support per-database and per-user GUC settings.  The functionality
available for handling GUC-ified variables is now so far superior to
plain SET that it's really foolish to consider having any parameters
that are outside GUC control.
        regards, tom lane