On Thu, 2010-05-13 at 21:15 -0400, Tom Lane wrote: > Greg Stark <gsst...@mit.edu> writes: > > On Thu, May 13, 2010 at 11:33 PM, Robert Haas <robertmh...@gmail.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/407d949e1002131017u657e4aefo2647c2cbf24fe...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
