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

Re: WAL shipping and ever expanding pg_xlog

From: "Michael Dengler" <michael(dot)dengler(at)gmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: WAL shipping and ever expanding pg_xlog
Date: 2007-06-13 13:44:14
Message-ID: e8733d090706130644m471b8690m9998ba2d30f6f747@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
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?

Thanks

Mike


On 6/13/07, Michael Dengler <michael(dot)dengler(at)gmail(dot)com> wrote:
>
> Hi,
>
> 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?
>
> Thanks
>
> Mike
>
>

In response to

Responses

pgsql-performance by date

Next:From: Vivek KheraDate: 2007-06-13 14:02:40
Subject: Re: Best use of second controller with faster disks?
Previous:From: Michael DenglerDate: 2007-06-13 13:35:27
Subject: WAL shipping and ever expanding pg_xlog

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