| From: | "MauMau" <maumau307(at)gmail(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | "Daniel Farina" <daniel(at)heroku(dot)com>, "Josh Berkus" <josh(at)agliodbs(dot)com>, "Jeff Janes" <jeff(dot)janes(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hard limit on WAL space used (because PANIC sucks) |
| Date: | 2013-06-08 23:22:50 |
| Message-ID: | E340AE4A63F7400B94B35969D52D431A@maumau |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: "Joshua D. Drake" <jd(at)commandprompt(dot)com>
> On 06/08/2013 07:36 AM, MauMau wrote:
>> 3. You cannot know the reason of archive_command failure (e.g. archive
>> area full) if you don't use PostgreSQL's server logging.
>> This is because archive_command failure is not logged in syslog/eventlog.
>
> Wait, what? Is this true (someone else?)
I'm sorry, please let me correct myself. What I meant is:
This is because the exact reason for archive_command failure (e.g. cp's
output) is not logged in syslog/eventlog. The fact itself that
archive_command failed is recorded.
Regards
MauMau
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MauMau | 2013-06-08 23:42:24 | Re: Hard limit on WAL space used (because PANIC sucks) |
| Previous Message | Jeff Janes | 2013-06-08 23:20:13 | Re: Hard limit on WAL space used (because PANIC sucks) |