Horton

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

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

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Smith <greg@2ndQuadrant.com>
Cc: Amit Kapila <amit.kapila@huawei.com>, "'Alvaro Herrera'" <alvherre@2ndQuadrant.com>, "'Robert Haas'" <robertmhaas@gmail.com>, "'Greg Stark'" <stark@mit.edu>, "'Andres Freund'" <andres@2ndQuadrant.com>, "'Boszormenyi Zoltan'" <zb@cybertec.at>, pgsql-hackers@postgresql.org
Date: 2013-03-22T04:58:05Z
Lists: pgsql-hackers 
Greg Smith <greg@2ndQuadrant.com> writes:
> On 3/21/13 10:39 PM, Amit Kapila wrote:
>> I feel giving Notice after every command doesn't look good, so may be we can
>> mention the same in documentation.

> I think that NOTICE after every command is the only way we'll make sure 
> to catch every user who should be notified about the feature's limitation.

We have been around on that type of proposal before.  A command that
issues a NOTICE as part of its *standard* behavior is really not going
to fly; the annoyance, talking-down-to-the-user factor is too high.

IOW, if you think the command needs that, then its design is broken
and you need to do better.

			regards, tom lane