Re: unite recovery.conf and postgresql.conf
| От | Tom Lane |
|---|---|
| Тема | Re: unite recovery.conf and postgresql.conf |
| Дата | |
| Msg-id | 10040.1316883845@sss.pgh.pa.us обсуждение |
| Ответ на | Re: unite recovery.conf and postgresql.conf (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: unite recovery.conf and postgresql.conf
Re: unite recovery.conf and postgresql.conf |
| Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Sep 23, 2011 at 6:55 PM, Tatsuo Ishii <ishii@postgresql.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
В списке pgsql-hackers по дате отправления: