OK....it looks like the slave machine has run out of space and that caused
the xlog files to pile up on the master.
Still...how do I prevent such all of the shipped WAL segments from remaining
on the slave machine? Do I need to retain every single one? Can they be
safely removed after the slave machine has restored the particular segment?
On 6/13/07, Michael Dengler <michael(dot)dengler(at)gmail(dot)com> wrote:
> I'm doing WAL shipping to do a warm standby system (8.2.4).
> The problem is that the pg_xlog dir on the master just gets bigger and
> bigger (never seems to truncate) and the corresponding archive directory on
> the slave also gets bigger and bigger. Is there a way to moderate this?
In response to
pgsql-performance by date
|Next:||From: Vivek Khera||Date: 2007-06-13 14:02:40|
|Subject: Re: Best use of second controller with faster disks?|
|Previous:||From: Michael Dengler||Date: 2007-06-13 13:35:27|
|Subject: WAL shipping and ever expanding pg_xlog|