From: Michael Dengler <michael.dengler@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: WAL shipping and ever expanding pg_xlog
Date: Wed, 13 Jun 2007 09:44:14 -0400
Message-ID: <e8733d090706130644m471b8690m9998ba2d30f6f747@mail.gmail.com> (raw)
In-Reply-To: <e8733d090706130635j57a62a52q578adf53a0ac9791@mail.gmail.com>
References: <e8733d090706130635j57a62a52q578adf53a0ac9791@mail.gmail.com>
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.dengler@gmail.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
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: michael.dengler@gmail.com
Subject: Re: WAL shipping and ever expanding pg_xlog
In-Reply-To: <e8733d090706130644m471b8690m9998ba2d30f6f747@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox