> 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.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

• another idea for changing global configuration settings from SQL at 2012-11-15 17:53:15 from Peter Eisentraut

Responses

• Re: another idea for changing global configuration settings from SQL at 2012-11-15 23:31:33 from Craig Ringer

pgsql-hackers by date

Next:	From: Kohei KaiGai	Date: 2012-11-15 18:44:46
	Subject: Re: ALTER command reworks
Previous:	From: Josh Berkus	Date: 2012-11-15 18:36:18
	Subject: Re: Materialized views WIP patch