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

Fujii Masao <masao.fujii@gmail.com>

From: Fujii Masao <masao.fujii@gmail.com>
To: Amit Kapila <amit.kapila@huawei.com>
Cc: cedric@2ndquadrant.com, pgsql-hackers@postgresql.org, Robert Haas <robertmhaas@gmail.com>, Greg Smith <greg@2ndquadrant.com>, Josh Berkus <josh@agliodbs.com>, Tom Lane <tgl@sss.pgh.pa.us>, Magnus Hagander <magnus@hagander.net>, Christopher Browne <cbbrowne@gmail.com>
Date: 2012-11-17T21:38:03Z
Lists: pgsql-hackers
On Sat, Nov 17, 2012 at 10:25 PM, Amit Kapila <amit.kapila@huawei.com> wrote:
> 1. have a system table pg_global_system_settings(key,value)

Do we really need to store the settings in a system table?
Since WAL would be generated when storing the settings
in a system table, this approach seems to prevent us from
changing the settings in the standby.

> 2. On SQL command execution, insert if the value doesn't exist or update if
> already existing.

This means that we should implement something like MERGE
command first?

Regards,

-- 
Fujii Masao