On Fri, Mar 23, 2012 at 11:03:27PM +0900, Fujii Masao wrote:
On Wed, Feb 29, 2012 at 5:48 AM, Fujii Masao masao.fu...@gmail.com wrote:
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
On 23 March 2012 14:03, Fujii Masao masao.fu...@gmail.com wrote:
On Thu, Mar 22, 2012 at 12:56 AM, Robert Haas robertmh...@gmail.com wrote:
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
On Fri, Mar 23, 2012 at 10:03 AM, Fujii Masao masao.fu...@gmail.com wrote:
On second thought, I found other issues about WAL archiving after
failover. So let me clarify the issues again.
Just after failover, there can be three kinds of WAL files in new
master's pg_xlog directory:
(1) WAL
On Thu, Mar 22, 2012 at 12:56 AM, Robert Haas robertmh...@gmail.com wrote:
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
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
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
