From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | andy(dot)shellam(at)mailnetwork(dot)co(dot)uk |
Cc: | Stefan(dot)Schmidt(at)schinkel(dot)de, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: 2,2gb of pg_xlog ?? |
Date: | 2006-06-22 14:03:04 |
Message-ID: | 20060622140304.GJ29883@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Andy Shellam wrote:
> Archive_command = "mv %p /your/backup/directory/%f"
Don't do this. Postgres itself will remove the file after the
archive_command has copied it elsewhere.
> Tip: if you're absolutely sure you will never need these transaction logs,
> you can use the following command to delete them when they're finished with:
>
> Archive_command = "rm -f %p"
Don't do this either. If you're not using PITR, just set a blank
archive_command and Postgres will delete the file as soon as it's not
needed anymore.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Hoover | 2006-06-22 14:12:04 | Re: 2,2gb of pg_xlog ?? |
Previous Message | Chris Hoover | 2006-06-22 13:52:34 | Question on failure during cluster operation |