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

Re: WAL shipping and ever expanding pg_xlog

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Michael Dengler" <michael(dot)dengler(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: WAL shipping and ever expanding pg_xlog
Date: 2007-06-13 15:29:19
Message-ID: b42b73150706130829y7d8f062bu35376a5066069096@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On 6/13/07, Michael Dengler <michael(dot)dengler(at)gmail(dot)com> wrote:
> 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?

Are you using the pg_standy utility?  It has options to control this...

merlin

In response to

Responses

pgsql-performance by date

Next:From: Michael DenglerDate: 2007-06-13 16:12:39
Subject: Re: WAL shipping and ever expanding pg_xlog
Previous:From: Joshua D. DrakeDate: 2007-06-13 15:08:56
Subject: Re: VACUUM vs auto-vacuum daemon

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