Re: pg_xlog not cleaned up

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Christian Kastner <techmail(at)kvr(dot)at>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_xlog not cleaned up
Date: 2006-07-31 21:16:57
Message-ID: 200607312116.k6VLGvL13375@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Christian Kastner wrote:
> Bruce Momjian wrote:
> > What PostgreSQL version are you using? I know the *.backup file removal
> > was added in 8.1:
> >
> > * Remove old "*.backup" files when we do pg_stop_backup() (Bruce)
> > This prevents a large number of "*.backup" files from existing in
> > "/pg_xlog".
> >
> > but the existance of the files should not cause problems.
>
> It's 8.1.4, running on FC 5.
>
> It does not cause any active problems, but the WAL archiving fails until
> the *.backup and *.done files are removed manually, after which all the
> "ready" WAL segments are archived away normally.
>
> The script I supply to archive_command just mounts a windows share,
> performs a cp (similar to the example in the PITR doc) and unmounts the
> share again.

Try removing the mount/unmount --- just keep the share mounted all the
time and see if it works. I think the archive system believes it can do
concurrent archive commands as long as different file names are used.

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Philippe Lang 2006-07-31 21:36:16 Intel commercial compiler
Previous Message Worky Workerson 2006-07-31 21:10:13 Dynamic pgplsql triggers