Skip site navigation (1) Skip section navigation (2)

Re: recovery.conf location

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: recovery.conf location
Date: 2010-09-27 01:12:11
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sun, Sep 26, 2010 at 8:56 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Yeah. The original design for recovery.conf envisioned that it has only
>> a short lifespan while you're doing an archive recovery. Putting
>> parameters for slave operation into it has contorted things beyond
>> recognition. I think we really need to take two steps back and
>> reconsider the whole "parameters" versus "status" distinction there.

> Perhaps we should consider folding recovery.conf into postgresql.conf.

To the extent that it carries long-lived parameters, that would be
sensible.  I think there's also a status component to what it's doing
though.  Also, if we're trying to put SR parameters somewhere other than
postgresql.conf, it might be better if the existing parameters migrated
there instead.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Gurjeet SinghDate: 2010-09-27 01:14:16
Subject: Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.
Previous:From: Tom LaneDate: 2010-09-27 01:09:35
Subject: Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group