On Wed, Oct 27, 2010 at 6:44 PM, Jaime Casanova <jaime@2ndquadrant.com> wrote:
> On Wed, Oct 27, 2010 at 6:18 PM, Daniel Farina <drfarina@acm.org> wrote:
>>
>> As a result, "aborting startup due to startup process failure" is seen
>> in the log, but not the messages seen in
>> xlog.c:readRecoveryCommandFile that triggered the failure.
>>
>
> can you explain what steps you did to reproduce this?
Gack. The problem was that postgresql.conf was sending information to
the syslog only. postmaster continues to write quite a few messages to
the terminal even when syslog is set as the log destination (the log
level was set to be quite verbose), and I never tipped myself off to
the fact that I'd have to check elsewhere to see the whole story.
My bad.
fdr