On 13/09/10 18:19, Tom Lane wrote:
> Heikki Linnakangas<heikki.linnakangas@enterprisedb.com> writes:
>> Yet another idea: Check in pg_ctl if recovery.conf is also present. If
>> it is, assume we're in recovery and don't print that warning. That would
>> be dead simple.
>
> +1. This sounds like a much more appropriate approach.
Hmm, looking at this more closely, I'm a bit confused. We already rename
away backup_label at the beginning of recovery. Under what circumstances
do we have a problem? This starts to seem like a complete non-issue to me.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com