Re: another idea for changing global configuration settings from SQL

From: Cédric Villemain <cedric(at)2ndquadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: another idea for changing global configuration settings from SQL
Date: 2012-11-15 18:06:48
Message-ID: 201211151906.48742.cedric@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Le jeudi 15 novembre 2012 18:53:15, Peter Eisentraut a écrit :
> 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?

I like the idea.
--
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - Développement, Expertise et Formation

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-11-15 18:13:07 Re: tuplesort memory usage: grow_memtuples
Previous Message Robert Haas 2012-11-15 18:04:18 Re: another idea for changing global configuration settings from SQL