Skip site navigation (1) Skip section navigation (2)

Re: another idea for changing global configuration settings from SQL

From: Craig Ringer <craig(at)2ndQuadrant(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: another idea for changing global configuration settings from SQL
Date: 2012-11-15 23:31:33
Message-ID: 50A57B55.4030205@2ndQuadrant.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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



In response to

pgsql-hackers by date

Next:From: Jeff DavisDate: 2012-11-15 23:35:37
Subject: Re: Materialized views WIP patch
Previous:From: Alvaro HerreraDate: 2012-11-15 22:39:26
Subject: Re: autovacuum truncate exclusive lock round two

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group