On Wed, Feb 29, 2012 at 5:48 AM, Fujii Masao <masao.fu...@gmail.com> wrote: > Hi, > > In streaming replication, after failover, new master might have lots > of un-applied > WAL files with old timeline ID. They are the WAL files which were recycled as > a > future ones when the server was running as a standby. Since they will never be > used later, they don't need to be archived after failover. But since they have > neither .ready nor .done file in archive_status, checkpoints after > failover newly > create .reacy files for them, and then finally they are archived. > Which might cause > disk I/O spike both in WAL and archive storage. > > To avoid the above problem, I think that un-applied WAL files with old > timeline ID > should be marked as already-archived and recycled immediately at the end of > recovery. Thought?
I'm not an expert on this, but that makes sense to me. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
