Re: Turning recovery.conf into GUCs

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Turning recovery.conf into GUCs
Date: 2013-10-21 20:57:45
Message-ID: 52659549.3070206@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> 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?

Well, I was just pointing out that it would make things *much* easier
for tool authors if conf.d were enabled by default, instead of disabled
by default. Then they could change tools to write a "recovery.conf"
file to conf.d.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Piotr Marcinczyk 2013-10-21 21:34:55 Add \i option to bring in the specified file as a quoted literal
Previous Message Peter Geoghegan 2013-10-21 20:43:28 Re: Add min and max execute statement time in pg_stat_statement