Skip site navigation (1) Skip section navigation (2)

Unnecessary WAL archiving after failover

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Unnecessary WAL archiving after failover
Date: 2012-02-29 10:48:36
Message-ID: CAHGQGwGQQLrODSVRb=HBTt6bj-dvz0NS=_jcNZRO9EMbUaLx0g@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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?

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Responses

pgsql-hackers by date

Next:From: Pavel StehuleDate: 2012-02-29 13:37:48
Subject: Re: review: CHECK FUNCTION statement
Previous:From: Pavel StehuleDate: 2012-02-29 10:37:46
Subject: Re: pgsql_fdw, FDW for PostgreSQL server

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group