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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Wong | 2007-06-13 16:33:22 | Re: dbt2 NOTPM numbers |
Previous Message | Merlin Moncure | 2007-06-13 15:29:19 | Re: WAL shipping and ever expanding pg_xlog |