Re: unite recovery.conf and postgresql.conf

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tatsuo Ishii <ishii(at)postgresql(dot)org>, josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: unite recovery.conf and postgresql.conf
Date: 2011-09-24 17:04:05
Message-ID: 10040.1316883845@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, Sep 23, 2011 at 6:55 PM, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
>> I'm not sure what you mean by "not deal with" but part of pgpool-II's
>> functionality assumes that we can easily generate recovery.conf. If
>> reconf.conf is integrated into postgresql.conf, we need to edit
>> postgresql.conf, which is a little bit harder than generating
>> recovery.conf, I think.

> Since we haven't yet come up with a reasonable way of machine-editing
> postgresql.conf, this seems like a fairly serious objection to getting
> rid of recovery.conf.

I don't exactly buy this argument. If postgresql.conf is hard to
machine-edit, why is recovery.conf any easier?

> What if we modified pg_ctl to allow passing configuration parameters
> through to postmaster,

You mean like pg_ctl -o?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2011-09-24 17:10:38 Re: Large C files
Previous Message Tom Lane 2011-09-24 17:01:38 Re: unite recovery.conf and postgresql.conf