Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have set up two servers running Postgres 9.1, with one configured as a hot standby for the other using streaming replication. Given that, is there any reason for me to be archiving my WAL files?

I'm aware that the archived WAL files allow me to "go back in time" to a previous snapshot of the database, but for my particular application, I have no need for such a feature as long as my standby is ok. Are there any other reasons to keep them?

share|improve this question
up vote 2 down vote accepted

If the only reason you're keeping the WAL files is for replication and not backup, then no, you don't need to keep them once they've been fully incorporated into the secondary server. My understanding is that archive_cleanup_command should be handling this.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.