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

Re: another idea for changing global configuration settings from SQL

From: Amit Kapila <amit(dot)kapila(at)huawei(dot)com>
To: "'Dimitri Fontaine'" <dimitri(at)2ndQuadrant(dot)fr>, "'Tom Lane'"<tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>, "'pgsql-hackers'"<pgsql-hackers(at)postgresql(dot)org>
Subject: Re: another idea for changing global configuration settings from SQL
Date: 2012-11-17 13:28:46
Message-ID: 005301cdc4c7$7954f7c0$6bfee740$@kapila@huawei.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Saturday, November 17, 2012 3:35 AM Dimitri Fontaine wrote:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> > Have you considered ALTER SYSTEM SET ... ?  We'd talked about that in
> > the context of the other patch, but it seems to fit much more
> naturally
> > with this one.  Or maybe ALTER GLOBAL SET or ALTER ALL SET.
> 
> I would paint that one ALTER SYSTEM SET and the file based one ALTER
> CONFIGURATION SET. No new keyword were armed in that proposal.

One more could be to have built-in function

pg_change_config(level,key,value)

level - PG_NEW_CONNECTION
      - PG_SYTEM_LEVEL

Level will distinguish how and when the value will be used.

With Regards,
Amit Kapila.



In response to

pgsql-hackers by date

Next:From: Hannu KrosingDate: 2012-11-17 13:30:27
Subject: Re: logical changeset generation v3 - comparison to Postgres-R change set format
Previous:From: Amit KapilaDate: 2012-11-17 13:25:34
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