From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: quoting and recovery.conf |
Date: | 2010-05-14 05:41:44 |
Message-ID: | 1273815704.308.3055.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 2010-05-13 at 21:15 -0400, Tom Lane wrote:
> Greg Stark <gsstark(at)mit(dot)edu> writes:
> > On Thu, May 13, 2010 at 11:33 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> >> I think we should add a TODO to parse recovery.conf with the same code
> >> we use to parse postgresql.conf, or possibly merge the two files.
> >> This issue was previously alluded to here:
> >>
> >> http://archives.postgresql.org/pgsql-hackers/2010-04/msg00211.php
>
> > And more than alluded to here:
>
> > http://archives.postgresql.org/message-id/407d949e1002131017u657e4aefo2647c2cbf24fe7b4@mail.gmail.com
>
> The main reason for having a separate recovery.conf file is that its
> existence is what drives the setting of InArchiveRecovery. If we were
> to devise some other trigger for that condition, it'd be possible to
> fold all those settings in as GUC variables.
And the removal of recovery.conf at end of recovery prevents the
re-entry into archive recovery if we crash.
--
Simon Riggs www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Anssi Kääriäinen | 2010-05-14 05:41:50 | Re: Row-level Locks & SERIALIZABLE transactions, postgres vs. Oracle |
Previous Message | Marc G. Fournier | 2010-05-14 05:29:39 | Re: List traffic |