| From: | Daniel Farina <drfarina(at)acm(dot)org> |
|---|---|
| To: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: An unfortunate logging behavior when (mis)configuring recovery.conf |
| Date: | 2010-10-28 03:13:13 |
| Message-ID: | AANLkTi=htttwugQqsLzUwUty=9A3ffX94cmcVZzOO_cq@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 27, 2010 at 6:44 PM, Jaime Casanova <jaime(at)2ndquadrant(dot)com> wrote:
> On Wed, Oct 27, 2010 at 6:18 PM, Daniel Farina <drfarina(at)acm(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-10-28 03:32:25 | Re: Re: Postgres insert performance and storage requirement compared to Oracle |
| Previous Message | Andrew Dunstan | 2010-10-28 03:02:01 | Re: Composite Types and Function Parameters |