Horton
Menu

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: Amit kapila <amit.kapila@huawei.com>, Greg Smith <greg@2ndQuadrant.com>, "'Robert Haas'" <robertmhaas@gmail.com>, "'Magnus Hagander'" <magnus@hagander.net>, "'Christopher Browne'" <cbbrowne@gmail.com>, "'PostgreSQL-development'" <pgsql-hackers@postgresql.org>
Date: 2012-11-13T18:16:11Z
Lists: pgsql-hackers 
Josh Berkus <josh@agliodbs.com> writes:
> I was imagining writing single, specific settings, which inevitably
> leads to one-setting-per-file, e.g.:

> SET PERSISTENT work_mem = 256MB;

> What Amit seems to be talking about is more EXPORT SETTINGS, where you
> dump all current settings in the session to a file.  This seems likely
> to produce accidental changes when the user writes out settings they've
> forgotten they changed.

Yeah.  It also seems to be unnecessarily different from the existing
model of SET.  I'd go with one-setting-per-command.

			regards, tom lane