> configuration data somewhere else, but we really need to be able to tell
> the difference between "starting PITR", "continuing PITR after a
> mid-recovery crash", and "finished PITR, up and running normally".
> A GUC is not a good way to do that.
Does a GUC make sense to you for how to handle standby/master for
replication?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com