...
> 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.
istm that with the recent discussion of transaction-fying SET variables
that table-fying some settable parameters may be appropriate. Leave out
the "foolish" from the discussion please ;)
- Thomas