Re: Turning recovery.conf into GUCs

From: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Turning recovery.conf into GUCs
Date: 2013-10-21 20:18:29
Message-ID: CAJKUy5h-2qb1=hcjh6fLfxmbcQ5HBXBH+N+e_m9gjVrx3VXA8g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 21, 2013 at 2:57 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> Jaime,
>
>>> And, as I said before, we need to do the GUC merger in the same release
>>> we introduce configuration directory (or after it).
>>>
>>
>> you mean the ALTER SYSTEM syntax? anyway, why that restriction?
>
> No, I'm referring to the proposal to have an automatically created and
> included conf.d directory for extra configuration files.
>

9.3 has include_dir and postgresql.conf has this setted:
"""
#include_dir = 'conf.d' # include files ending in '.conf' from
# directory 'conf.d'
"""

anything before this should be up to the packagers, no?

or, do you mean something else?

--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566 Cell: +593 987171157

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-10-21 20:36:41 Re: Add min and max execute statement time in pg_stat_statement
Previous Message Tom Lane 2013-10-21 20:01:41 Re: Add min and max execute statement time in pg_stat_statement