On 11/16/2012 02:38 AM, Josh Berkus wrote: >> ApplySetting(InvalidOid, InvalidOid, relsetting, PGC_S_$SOMETHING); >> >> in postinit.c, and have some SQL command to modify this setting. >> >> The only thing you couldn't handle that way are SIGHUP settings, but the >> often-cited use cases work_mem, logging, etc. would work. >> >> There would also be the advantage that pg_dumpall would save these settings. > I think this is a great idea. > > One caveat: we really, really, really need a system view which allows > DBAs to easily review settings defined for specific users and databases. > Right now, it requires significant pg_catalog hacking expertise to pull > out user-specific settings.
A system information function like settings_for_user('username') would certainly be welcome, showing: setting_name setting_value setting_origin -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers