| From: | Wayne Conrad <wconrad(at)yagni(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_xlog not cleaned up |
| Date: | 2006-07-31 22:11:08 |
| Message-ID: | 20060731221108.GB23659@yagni.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jul 31, 2006 at 10:18:31PM +0200, Christian Kastner wrote:
> After the online backup script runs, all subsequent attempts to run
> archive_command fail because the first thing it tries to archive away is
> the still-existing *.backup file. This fails because a copy already
> exists in the archive area and the script refuses to overwrite the
> existing file.
I'm seeing this too. I thought I was doing something wrong.
In case more info will help Those Who Know Things:
My archive_command is a simple copy to the same storage device, pretty
much right lifted out of the manual:
archive_command = 'test ! -f /var/lib/postgresql/8.1/pitr/current/wal/%f && cp
+%p /var/lib/postgresql/8.1/pitr/current/wal/%f'
Version: Postgres 8.1.3-4, i386, Debian testing.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2006-08-01 00:53:34 | Re: pg_xlog not cleaned up |
| Previous Message | Francisco Reyes | 2006-07-31 22:09:33 | Re: Corrupted DB? could not open file pg_clog/#### |