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: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: WAL shipping and ever expanding pg_xlog
Date: 2007-06-13 16:12:39
Message-ID: e8733d090706130912g794e5062hb0e95470eec6481c@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
Doug Knight just informed me about the pg_standby module.

Works like a charm!

Thanks

Mike


On 6/13/07, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
>
> 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

pgsql-performance by date

Next:From: Mark WongDate: 2007-06-13 16:33:22
Subject: Re: dbt2 NOTPM numbers
Previous:From: Merlin MoncureDate: 2007-06-13 15:29:19
Subject: Re: WAL shipping and ever expanding pg_xlog

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