Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: Fujii Masao <masao.fujii@gmail.com>, Dimitri Fontaine <dfontaine@hi-media.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-02-12T13:10:21Z
Lists: pgsql-hackers
Simon Riggs wrote: > In 8.4 it is pg_standby that was responsible for clearing down the > archive, which is why I suggested using pg_standby for that again. I > agree that will not work. The important thing is not pg_standby but that > we have a valid mechanism for clearing down the archive. Good point. When streaming from the master, the standby doesn't call restore_command, and restore_command doesn't get a chance to clean up old files. > So I suggest that you have a new action that gets called after every > checkpoint to clear down the archive. It will remove all files from the > archive prior to %r. We can implement that as a sequence of unlink()s > from within the server, or we can just call a script to do it. I prefer > the latter approach. However we do it, we need something initiated by > the server to maintain the archive and stop it from overflowing. +1 -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com