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

Re: Proposal for Allow postgresql.conf values to be changed via SQL

From: Amit kapila <amit(dot)kapila(at)huawei(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "'Christopher Browne'" <cbbrowne(at)gmail(dot)com>
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL
Date: 2012-11-01 04:00:05
Message-ID: 6C0B27F7206C9E4CA54AE035729E9C382854650E@szxeml509-mbx (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Wednesday, October 31, 2012 10:21 PM Josh Berkus wrote:

> I think you can simplify this task by forgetting about parsing the .auto
> file entirely when writing it.  That is, the .auto file should be
> regenerated, and should write out whatever has been set in pg_settings,
> regardless of what was in the file beforehand.  I don't see the value in
> parsing the file before writing it out.

   In that case how the new value of config parameter as set by user, will go in .auto file.
   Shall we change in guc, from where pg_settings take the values?

   Another point is curretly pg_settings doesn't have comments, so user will not be allowed to give comments with new value of config parameter.
   Is that okay?

With Regards,
Amit Kapila.

In response to

pgsql-hackers by date

Next:From: David FetterDate: 2012-11-01 04:03:03
Subject: Re: Synchronous commit not... synchronous?
Previous:From: Peter van HardenbergDate: 2012-11-01 01:39:20
Subject: Synchronous commit not... synchronous?

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