Re: Cleanup of same archive used by multiple standbys

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "PG Admin" <pgsql-admin(at)postgresql(dot)org>,"A J" <s5aly(at)yahoo(dot)com>
Subject: Re: Cleanup of same archive used by multiple standbys
Date: 2011-08-10 17:00:07
Message-ID: 4E4272C7020000250003FD48@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

A J <s5aly(at)yahoo(dot)com> wrote:

> Also couple of additional related question:
> 2. Am I correct in my assumption that if for some reason archive
> is not cleaned up and runs out of space, the WALs will accumulate
> in pg_xlog directory on the primary. If pg_xlog was to then run
> out of space, Primary server will stop accepting new writes and
> fail ?

That sounds correct to me. I've never seen it in practice, though;
we would need to ignore alerts from our monitoring for quite some
time before it got to that point.

> 3. If my standbys are in different datacenter, what is the
> suggested location of the archive directory ? Is it recommended to
> have it local in the data center of the primary server or somehow
> have it over in the remote data center.

In our shop we have found it advantageous to immediately write it
locally, and then use rsync (through ssh and a daemon) to bring the
remote site(s) into sync.

-Kevin

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message c k 2011-08-10 17:00:30 Re: postgresql server crash on windows 7 when using plpython
Previous Message Kevin Grittner 2011-08-10 16:53:13 Re: Cleanup of same archive used by multiple standbys