Received: from localhost (maia-4.hub.org [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id AB6A99FBC42
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Wed, 13 Jun 2007 10:44:19 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 19319-03 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Wed, 13 Jun 2007 10:44:16 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5
Received: from an-out-0708.google.com (an-out-0708.google.com
 [209.85.132.242])
	by postgresql.org (Postfix) with ESMTP id 744939FBC45
	for <pgsql-performance@postgresql.org>;
	Wed, 13 Jun 2007 10:44:16 -0300 (ADT)
Received: by an-out-0708.google.com with SMTP id c36so40141ana
	for <pgsql-performance@postgresql.org>;
	Wed, 13 Jun 2007 06:44:15 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
	b=G9y4HImuZcWvNkF8pFhKusa81Gyvm3OYGCJd/hZFfSpvVaqGRQVwSiPE6kw1NxwjIVtZhLxqihH09EyeyKhvx06bbZFFCS0XFFgQBxAbzSoay9XjUeemDJrBc1mWAvAQ/CRzzqCDFDYVLrOejjXYRRgpxgl7pGDRmE1VI5kLqmE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
	b=n2dJ0o9yovnuo0Z/BfSpJBu1JeVzAMXeUdfmWtXCzefQSqoyP+nyxXdI5q/9/w6+aDteIxnH9UWiAplh9oA5OxHP9yfmt1Ljk4229n9rfZK8JpeJUEYs72y5PnDjkxZ1x+WHNnpZ3IupG1d/cW+Nz0hKhz71tEydjQ5oRKsM/xo=
Received: by 10.100.197.15 with SMTP id u15mr362125anf.1181742254669;
	Wed, 13 Jun 2007 06:44:14 -0700 (PDT)
Received: by 10.100.134.10 with HTTP; Wed, 13 Jun 2007 06:44:14 -0700 (PDT)
Message-ID: <e8733d090706130644m471b8690m9998ba2d30f6f747@mail.gmail.com>
Date: Wed, 13 Jun 2007 09:44:14 -0400
From: "Michael Dengler" <michael.dengler@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: WAL shipping and ever expanding pg_xlog
In-Reply-To: <e8733d090706130635j57a62a52q578adf53a0ac9791@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_28181_4912207.1181742254642"
References: <e8733d090706130635j57a62a52q578adf53a0ac9791@mail.gmail.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200706/234
X-Sequence-Number: 25267

------=_Part_28181_4912207.1181742254642
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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
>
>

------=_Part_28181_4912207.1181742254642
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

OK....it looks like the slave machine has run out of space and that caused the xlog files to pile up on the master.<br><br>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?
<br><br>Thanks<br><br>Mike<br><br><br><div><span class="gmail_quote">On 6/13/07, <b class="gmail_sendername">Michael Dengler</b> &lt;<a href="mailto:michael.dengler@gmail.com">michael.dengler@gmail.com</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br><br>I&#39;m doing WAL shipping to do a warm standby system (8.2.4).<br><br>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? 
<br><br>Thanks<br><br>Mike<br><br>
</blockquote></div><br>

------=_Part_28181_4912207.1181742254642--