Re: recovery.conf location - Mailing list pgsql-hackers

From Tom Lane
Subject Re: recovery.conf location
Date
Msg-id 21208.1285968022@sss.pgh.pa.us
Whole thread Raw
In response to Re: recovery.conf location  (Josh Berkus <josh@agliodbs.com>)
Responses Re: recovery.conf location  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
> Then instead of having a trigger file, the admin could just update the
> status file in recovery.conf and save it (or overwrite the file).

This doesn't seem like a terribly bright idea.  We've expended megabytes
of list traffic on arguing about automatic updates of config files, and
still don't have a generally acceptable solution.  Now you want to make
standby-mode transitions contingent on solving that problem?

Keep the state separate from the config, please.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: recovery.conf location
Next
From: Greg Stark
Date:
Subject: Re: git diff --patience