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

Re: another idea for changing global configuration settings from SQL

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: another idea for changing global configuration settings from SQL
Date: 2012-11-15 18:04:18
Message-ID: CA+TgmoaRVaLCX+GL77i1Jv9XJLZwjZe3v=z27FML6Dys6KLf2A@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Nov 15, 2012 at 12:53 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> 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?

Personally, I think that would be wonderful.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


In response to

pgsql-hackers by date

Next:From: Cédric VillemainDate: 2012-11-15 18:06:48
Subject: Re: another idea for changing global configuration settings from SQL
Previous:From: Cédric VillemainDate: 2012-11-15 17:58:06
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL

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