> Don't do this. Postgres itself will remove the file after the > archive_command has copied it elsewhere. In my 8.1.3 install, it didn't - when I specified a cp command, it left the files there. I had to define the command as "mv" to have them moved. > 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. Why not, what's the difference? Surely Postgres just calls a similar "rm" kernel call to remove the file anyway? > -----Original Message----- > From: pgsql-admin-owner@xxxxxxxxxxxxxx [mailto:pgsql-admin- > owner@xxxxxxxxxxxxxx] On Behalf Of Alvaro Herrera > Sent: 22 June 2006 3:03 pm > To: andy.shellam@xxxxxxxxxxxxxxxxx > Cc: Stefan.Schmidt@xxxxxxxxxxx; pgsql-admin@xxxxxxxxxxxxxx > Subject: Re: [ADMIN] 2,2gb of pg_xlog ?? > > 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 > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster > > !DSPAM:14,449aa37b256841438716522! >
