Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id B563A1337BD5 for ; Wed, 23 Mar 2011 18:21:36 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 44671-01-2 for ; Wed, 23 Mar 2011 21:21:18 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-wy0-f174.google.com (mail-wy0-f174.google.com [74.125.82.174]) by mail.postgresql.org (Postfix) with ESMTP id E405E1337C47 for ; Wed, 23 Mar 2011 18:16:57 -0300 (ADT) Received: by wya21 with SMTP id 21so8044445wya.19 for ; Wed, 23 Mar 2011 14:16:57 -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:subject:x-mailer :mime-version:content-type:content-transfer-encoding; bh=55RcZYp0JXEX6GF5QCXeWR0T+BVLtdvzAOJincBCPzo=; b=MdemJvkLxWT5kWkTOHrlN3a8qPUOtRkI8tbr5Jme00pP3CRenGPFKLbkqcMJ6urSwK YOo5gAIKDmiSbejwAoXJ8OgGb/x4pPVgOhElPIxvSz7PIjHMhHU6tKbYL96pf2fY3+iD v8o/ry55XNCEbnGr60jFTtUgH4yCY6zuPFA1M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:message-id:subject:x-mailer:mime-version:content-type :content-transfer-encoding; b=otR5WJM7fEYRdCQiqYUGzVAJZ0B8ivuR7jeOC9/F93yUiajF/lOIWBJ/nMdPgkodxl ih2U+fkQ3rFx0CQAypwOnG9tQMItJphGs5EhtuaG9lIuaBMVpdQGJcEHVdeYxSbEYTPz zHM5R2dAfIIhuM4q/wO9OtUYhP47ORdZU7HUc= Received: by 10.216.51.135 with SMTP id b7mr302695wec.29.1300915017140; Wed, 23 Mar 2011 14:16:57 -0700 (PDT) Received: from Fruitybook.local (16.245.146.195.dynamic.adsl.abo.nordnet.fr [195.146.245.16]) by mx.google.com with ESMTPS id bs4sm2118396wbb.35.2011.03.23.14.16.54 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 23 Mar 2011 14:16:55 -0700 (PDT) Date: Wed, 23 Mar 2011 22:16:51 +0100 From: Simon Luijk To: pgsql-admin@postgresql.org Message-ID: <3F0EEA129881413DBA589A6EE13EBED6@gmail.com> Subject: 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="4d8a6343_14fce74e_e7" Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.588 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, T_TO_NO_BRKTS_FREEMAIL=0.01 X-Spam-Level: X-Archive-Number: 201103/218 X-Sequence-Number: 37090 --4d8a6343_14fce74e_e7 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Content-Disposition: inline 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 --4d8a6343_14fce74e_e7 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
I have a master slave setup that is on the most pa= rt 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=5Fxlog dir and not overwriting. I do have
archive=5Fmode 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 to= o=3F

Thanks in advance
Simon
--4d8a6343_14fce74e_e7--