Heikki Linnakangas <heikki.linnakan...@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.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
