Re: Proposal for Allow postgresql.conf values to be changed via SQL - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Proposal for Allow postgresql.conf values to be changed via SQL
Date
Msg-id 509045C3.80807@agliodbs.com
Whole thread Raw
In response to Re: Proposal for Allow postgresql.conf values to be changed via SQL  (Chris Corbyn <chris@w3style.co.uk>)
Responses Re: Proposal for Allow postgresql.conf values to be changed via SQL  (Christopher Browne <cbbrowne@gmail.com>)
List pgsql-hackers
On 10/29/12 6:40 AM, Chris Corbyn wrote:
> What's the use case of this? It sounds like it will just create a maintenance nightmare where some stuff you expect
tolookup in in postgresql.conf is actually hiding in the .auto file. Assuming only super users/sysadmins would have the
abilityto change things in the config file, wouldn't they be more likely to just do it on the server and edit the .conf
(whichamong other things, keeps it tidy and orderly).
 

The use is the ability to manage dozens, or hundreds, of PostgreSQL
servers via Port 5432.  It would also make writing an auto-configurator
easier.

I agree that there's not much benefit if you're only managing a single
PostgreSQL server.  There's a lot of benefit for those of us who have to
manage a lot of them though.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: Extensions Documentation
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Preserve intermediate .c files in coverage mode