Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id C5DEB133740B
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Sat, 26 Mar 2011 08:39:49 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 79410-07 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Sat, 26 Mar 2011 11:39:39 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-fx0-f46.google.com (mail-fx0-f46.google.com
	[209.85.161.46])
	by mail.postgresql.org (Postfix) with ESMTP id AFC201337990
	for <pgsql-admin@postgresql.org>; Sat, 26 Mar 2011 08:39:37 -0300 (ADT)
Received: by fxm17 with SMTP id 17so1704282fxm.19
	for <pgsql-admin@postgresql.org>; Sat, 26 Mar 2011 04:39:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:date:from:to:message-id:in-reply-to:references
	:subject:x-mailer:mime-version:content-type
	:content-transfer-encoding;
	bh=LNvMVMz52Pao2pxIqnThNPQ1iiqN28sFvfEZpVuArC0=;
	b=CWiqXMYrx3uJL3CIbD5twZgRwyZwVSJbKr7+NvqLIk11Y40n4LawD5clTX8zAJ4GXG
	f+DsoUTUc8QMyk64dtYoZ096a8Ex1vr4xkY6z2BZ/jukphEAj2IIZCQSaAJl0INhh/Y3
	/84X4KgrY1qs/NexqOtXgvVw9/yJAAxWQATOs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=date:from:to:message-id:in-reply-to:references:subject:x-mailer
	:mime-version:content-type:content-transfer-encoding;
	b=EEIQNO8lmL0ejPNBZa6ApcPdsgAlKiYhsRmFXTKW5tkdTnbBxyvlP2CVKkyajRcm3f
	hy9ld5Z6ON7L7dBSyfDV9e7jLidTtBpJoTWiKypQ/OAJWG2l0U44ZYrC4EiYwBanvj0+
	ty7XGA8FR63W/tjdyrD51HNorVJzO/c371osE=
Received: by 10.223.59.146 with SMTP id l18mr2125490fah.58.1301139577097;
	Sat, 26 Mar 2011 04:39:37 -0700 (PDT)
Received: from Fruitybook.local (203.250.146.195.dynamic.adsl.abo.nordnet.fr
	[195.146.250.203])
	by mx.google.com with ESMTPS id f15sm759417fax.34.2011.03.26.04.39.35
	(version=TLSv1/SSLv3 cipher=OTHER);
	Sat, 26 Mar 2011 04:39:36 -0700 (PDT)
Date: Sat, 26 Mar 2011 12:39:33 +0100
From: Simon Luijk <simonluijk@gmail.com>
To: pgsql-admin@postgresql.org
Message-ID: <5D504653F701441CA322FE5E861DFE7D@gmail.com>
In-Reply-To: <3F0EEA129881413DBA589A6EE13EBED6@gmail.com>
References: <3F0EEA129881413DBA589A6EE13EBED6@gmail.com>
Subject: Re: Wal archives building up in slave pg_xlog dir
X-Mailer: sparrow 1.0.1 (build 589.15)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4d8dd075_5072367_dd"
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.888 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001,
	T_TO_NO_BRKTS_FREEMAIL=0.01
X-Spam-Level: 
X-Archive-Number: 201103/246
X-Sequence-Number: 37118

--4d8dd075_5072367_dd
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline

So I have turned archive_mode off on the slave. At first I thought this solved it but
the logs are still building up. Could anyone shed some light on why the logs are building
up in pg_xlog?

Thank you
Simon
On Wednesday, 23 March 2011 at 22:16, Simon Luijk wrote: 
> I have a master slave setup that is on the most part working smoothly. The logs are getting
> shipped to the slave, the slave is requesting them and then applying them.
> 
> The problem is that the logs are building up in the pg_xlog dir and not overwriting. I do have
> archive_mode on in postgresql.conf so when the slave needs to come online as the new
> primary it start shipping its logs. Is this setting effecting recovery mode too?
> 
> Thanks in advance
> Simon
> 
> 
> 
> 


--4d8dd075_5072367_dd
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div>
            <div><span>So I have turned archive=5Fmode off on the slave. =
At first I thought this solved it but</span></div><div><span>the logs are=
 still building up. Could anyone shed some light on why the logs are buil=
ding</span></div><div><span>up in pg=5Fxlog=3F</span></div><div><span><br=
></span></div><div><span>Thank you</span></div><div><span>Simon<br></span=
>
               =20
                <p style=3D=22color: =23a0a0a0;=22>On Wednesday, 23 March=
 2011 at 22:16, Simon Luijk wrote:</p>
                <blockquote type=3D=22cite=22 style=3D=22border-left-styl=
e:solid;border-width:1px;margin-left:0px;padding-left:10px;=22>
                    <span><div><div><div>
            <div><span>I have a master slave setup that is on the most pa=
rt working smoothly. The logs are getting</span></div><div><span>shipped =
to the slave, the slave is requesting them and then applying them.</span>=
</div><div><span><br></span></div><div><span>The problem is that the logs=
 are building up in the pg=5Fxlog dir and not overwriting. I do have</spa=
n></div><div><span>archive=5Fmode on in postgresql.conf so when the slave=
 needs to come online as the new</span></div><div><span>primary it start =
shipping&nbsp;</span>its logs. Is this setting effecting recovery mode to=
o=3F</div><div><br></div><div>Thanks in advance</div><div>Simon</div>
        </div></div></div></span>
               =20
               =20
               =20
               =20
                </blockquote>
               =20
                <div>
                    <br>
                </div>
            </div>
        </div>
--4d8dd075_5072367_dd--