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

From Josh Berkus
Subject Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Date
Msg-id 51E8B422.3090908@agliodbs.com
Whole thread Raw
In response to Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])  (Amit kapila <amit.kapila@huawei.com>)
List pgsql-hackers
Greg,

> I thought this was a good spot to try and re-draw this line because I
> don't want just one program that is able to create new configuration
> entries easily.  I want to see a whole universe of them.  ALTER SYSTEM
> SET, tuning helpers, replication helpers, logging helpers, vacuum
> schedulers.  All of them *could* just dump a simple file into a config
> directory with code anyone can write.  And having ALTER SYSTEM SET do
> that provides a strong precedent for how it can be done.  (I'd like to
> see initdb do that instead of hacking the system postgresql.conf as if
> sed-style edits were still the new hotness, but that's a future change)

Thank you.  I wanted to say this, but I couldn't find a way to express it.

> Some of them didn't get the memo that the right standard name is conf.d
> now, but they're the minority.

Apparently we didn't get the memo either.


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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgindent behavior we could do without
Next
From: Noah Misch
Date:
Subject: Re: getting rid of SnapshotNow