Re: RFC: programmable file format for postgresql.conf

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Álvaro Hernández Tortosa <aht(at)nosys(dot)es>
Cc: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: RFC: programmable file format for postgresql.conf
Date: 2013-12-06 03:47:29
Message-ID: 1386301649.2743.20.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2013-12-05 at 00:51 +0100, Álvaro Hernández Tortosa wrote:
> In return for this extra information, we:
>
> - Provide users with more help (information) to help them configure
> postgres (which is no easy task, specially for newcomers).
>
> - Help and encourage app developers to create both GUI tools for
> easier
> postgresql configuration and automatic or semi-automatic
> configuration
> tools.
>
> - Make it way easier to change postgresql parameters persistently from
> a
> SQL connection.
>
> The tradeoff seems quite positive to me. I see no strong
> reasons why
> not do it... am I missing something?

I don't buy your argument. You say, if we make this change, those
things will happen. I don't believe it. You can *already* do those
things, but no one is doing it.

But if we make this change, existing users will be inconvenienced,
whereas the expected benefits are very much in doubt. Again, this is
postgres --describe-config all over again.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabrízio de Royes Mello 2013-12-06 04:07:15 Re: Time-Delayed Standbys
Previous Message Peter Eisentraut 2013-12-06 03:37:30 Re: Performance optimization of btree binary search