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: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
Cc: 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 00:56:53
Message-ID: 20737.1285549013@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Jaime Casanova <jaime(at)2ndquadrant(dot)com> writes:
> On Sun, Sep 26, 2010 at 6:29 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>> On Mon, Sep 27, 2010 at 6:56 AM, Thom Brown <thom(at)linux(dot)com> wrote:
>>> I noticed that there's no way to specify the location of recovery.conf
>>> in postgresql.conf.

>> +1
>> 
>> That parameter would be useful when user makes multiple standbys see
>> the same recovery.conf located in NFS or elsewhere.

> Maybe i'm missing something but this would be a problem if we put a
> trigger file and the recovery.conf gets renamed to recovery.done, no?

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.

This is pretty tightly tied to the ongoing argument about where to keep
parameters for synchronous replication, too.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-09-27 01:03:24
Subject: Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.
Previous:From: Jaime CasanovaDate: 2010-09-27 00:35:35
Subject: Re: recovery.conf location

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