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

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: 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-18 22:03:36
Message-ID: 20130718220336.GA4139@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus escribió:

> We are missing one feature, which is the ability to relocate the
> postgresql.auto.conf file if relocating it is desireable according to
> some sysadmin spec. This kind of ties into another patch which was
> discussed on this list -- the ability to relocate the recovery.conf
> file.

Well, postgresql.conf is already relocatable. Is there any advantage in
being able to move postgresql.auto.conf to a different location than
postgresql.conf? I don't see any. I didn't follow the recovery.conf
discussion, but I imagine that the reason for wanting to be able to
relocate it is related to standby vs. master distinction. This doesn't
apply to postgresql.auto.conf, I think, does it?

If people want to drill real down, they can always have a
postgresql.auto.conf that's a symlink. (In this light, we would ship an
empty postgresql.auto.conf in a freshly initdb'd system. IIRC the
current patch already does that.)

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2013-07-18 22:15:07 Re: [9.4 CF 1] Patches which desperately need code review
Previous Message Josh Berkus 2013-07-18 21:31:11 [9.4 CF 1] Patches which desperately need code review