Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])

From: Greg Smith <greg(at)2ndQuadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Date: 2013-08-03 06:54:25
Message-ID: 51FCA921.1040708@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/2/13 4:48 PM, Stephen Frost wrote:
> * Josh Berkus (josh(at)agliodbs(dot)com) wrote:
>> I really think this is the wrong approach. If we start removing
>> "unsafe" parameters from ALTER SYSTEM SET, we basically hobble the
>> feature to the point of uselessness. Out of the 15 or so parameters 80%
>> of our users touch, half of them are on your "unsafe" list.
>
> Reflecting on this a bit more, I'm curious what your list-of-15 is.

You can get a top 15-ish list from
https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server

The list of things I see changed regularly that are on your unsafe list are:

listen_addresses, port, shared_buffers, log_directory, log_filename

Obvious missing thing from your unsafe list that is also changed
regularly is max_connection. I count 6 parameters that are both unsafe
and changed regularly.

--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomonari Katsumata 2013-08-03 07:31:49 Re: comment for "fast promote"
Previous Message Bruce Momjian 2013-08-03 03:47:03 Re: 9.3beta2: Failure to pg_upgrade