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

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Greg Smith <greg(at)2ndQuadrant(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
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: 2013-07-19 03:36:02
Message-ID: 51E8B422.3090908@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message amulsul 2013-07-19 03:40:16 Re: Fatal error after starting postgres : sys identifiers must be different
Previous Message Tom Lane 2013-07-19 03:30:11 Re: pgindent behavior we could do without