pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
WAL shipping and ever expanding pg_xlog
4+ messages / 2 participants
[nested] [flat]

* WAL shipping and ever expanding pg_xlog
@ 2007-06-13 13:35 Michael Dengler <michael.dengler@gmail.com>
  2007-06-13 13:44 ` Re: WAL shipping and ever expanding pg_xlog Michael Dengler <michael.dengler@gmail.com>
  0 siblings, 1 reply; 4+ messages in thread

From: Michael Dengler @ 2007-06-13 13:35 UTC (permalink / raw)
  To: pgsql-performance

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

^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: WAL shipping and ever expanding pg_xlog
  2007-06-13 13:35 WAL shipping and ever expanding pg_xlog Michael Dengler <michael.dengler@gmail.com>
@ 2007-06-13 13:44 ` Michael Dengler <michael.dengler@gmail.com>
  2007-06-13 15:29   ` Re: WAL shipping and ever expanding pg_xlog Merlin Moncure <mmoncure@gmail.com>
  0 siblings, 1 reply; 4+ messages in thread

From: Michael Dengler @ 2007-06-13 13:44 UTC (permalink / raw)
  To: 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.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
>
>

^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: WAL shipping and ever expanding pg_xlog
  2007-06-13 13:35 WAL shipping and ever expanding pg_xlog Michael Dengler <michael.dengler@gmail.com>
  2007-06-13 13:44 ` Re: WAL shipping and ever expanding pg_xlog Michael Dengler <michael.dengler@gmail.com>
@ 2007-06-13 15:29   ` Merlin Moncure <mmoncure@gmail.com>
  2007-06-13 16:12     ` Re: WAL shipping and ever expanding pg_xlog Michael Dengler <michael.dengler@gmail.com>
  0 siblings, 1 reply; 4+ messages in thread

From: Merlin Moncure @ 2007-06-13 15:29 UTC (permalink / raw)
  To: Michael Dengler <michael.dengler@gmail.com>; +Cc: pgsql-performance

On 6/13/07, Michael Dengler <michael.dengler@gmail.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



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: WAL shipping and ever expanding pg_xlog
  2007-06-13 13:35 WAL shipping and ever expanding pg_xlog Michael Dengler <michael.dengler@gmail.com>
  2007-06-13 13:44 ` Re: WAL shipping and ever expanding pg_xlog Michael Dengler <michael.dengler@gmail.com>
  2007-06-13 15:29   ` Re: WAL shipping and ever expanding pg_xlog Merlin Moncure <mmoncure@gmail.com>
@ 2007-06-13 16:12     ` Michael Dengler <michael.dengler@gmail.com>
  0 siblings, 0 replies; 4+ messages in thread

From: Michael Dengler @ 2007-06-13 16:12 UTC (permalink / raw)
  To: Merlin Moncure <mmoncure@gmail.com>; +Cc: 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@gmail.com> wrote:
>
> On 6/13/07, Michael Dengler <michael.dengler@gmail.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
>

^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2007-06-13 16:12 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2007-06-13 13:35 WAL shipping and ever expanding pg_xlog Michael Dengler <michael.dengler@gmail.com>
2007-06-13 13:44 ` Michael Dengler <michael.dengler@gmail.com>
2007-06-13 15:29   ` Merlin Moncure <mmoncure@gmail.com>
2007-06-13 16:12     ` Michael Dengler <michael.dengler@gmail.com>

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