From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | another idea for changing global configuration settings from SQL |
Date: | 2012-11-15 17:53:15 |
Message-ID: | 50A52C0B.9080505@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Independent of the discussion of how to edit configuration files from
SQL, I had another idea how many of the use cases for this could be handled.
We already have the ability to store in pg_db_role_setting configuration
settings for
specific user, specific database
specific user, any database
any user, specific database
The existing infrastructure would also support
any user, any database (= all the time)
All you'd need is to add
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.
Thoughts?
From | Date | Subject | |
---|---|---|---|
Next Message | Kohei KaiGai | 2012-11-15 17:53:46 | Re: [v9.3] writable foreign tables |
Previous Message | Peter Geoghegan | 2012-11-15 17:29:19 | Re: tuplesort memory usage: grow_memtuples |