How can the archive process fall behind? Postgres will never reuse WAL files which are not yet archived.
Regarding your question about slowing down WAL generation, that is not possible to do, unless you slow down the application which is doing the writing into the database.
Hi I am working with version 9.1.9. The dabase is in archiving mode. The archives are then sended to a hotstandby replication sever.
I have seen that under heavy load, the archive process will fall behind the WAL generation and thuse some WAL segments won't get archived so the replication stops. To recover from this I need to do a new cold backup and send it to the replication server. Is there a way to limit the WAL generation (i.e slowing down insterts and deletes) so as to prevent the archive from falling behind?
