From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | MauMau <maumau307(at)gmail(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 18:07:34 |
Message-ID: | 51B372E6.8080604@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 06/08/2013 07:36 AM, MauMau wrote:
> 1. If the machine or postgres crashes while archive_command is copying a
> WAL file, later archive recovery fails.
> This is because cp leaves a file of less than 16MB in archive area, and
> postgres refuses to start when it finds such a small archive WAL file.
> The solution, which IIRC Tomas san told me here, is to do like "cp %p
> /archive/dir/%f.tmp && mv /archive/dir/%f.tmp /archive/dir/%f".
Well it seems to me that one of the problems here is we tell people to
use copy. We should be telling people to use a command (or supply a
command) that is smarter than that.
> 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?)
JD
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2013-06-08 18:15:40 | Re: Hard limit on WAL space used (because PANIC sucks) |
Previous Message | Joshua D. Drake | 2013-06-08 18:05:04 | Re: Hard limit on WAL space used (because PANIC sucks) |