Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bICJg-0006f5-IN for pgsql-performance@arkaria.postgresql.org; Wed, 29 Jun 2016 10:01:56 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bICJf-0003th-Ln for pgsql-performance@arkaria.postgresql.org; Wed, 29 Jun 2016 10:01:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bICHz-0001ty-5R for pgsql-performance@postgresql.org; Wed, 29 Jun 2016 10:00:11 +0000 Received: from mail-lf0-x22f.google.com ([2a00:1450:4010:c07::22f]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bICHr-00063A-BI for pgsql-performance@postgresql.org; Wed, 29 Jun 2016 10:00:10 +0000 Received: by mail-lf0-x22f.google.com with SMTP id q132so29674398lfe.3 for ; Wed, 29 Jun 2016 03:00:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=autouncle-com.20150623.gappssmtp.com; s=20150623; h=from:subject:message-id:date:to:mime-version; bh=smSRZYY/PCIpmyps5t7EimA5rrltI4laUcpLxuwnauA=; b=NEu63JWp3EUNP+WuMwLiEgnj09/v9emn/iHj6+QoN8MtPNN0ZhvAthqJD/OOB/8Cv+ noTizxeVL0taqqxg8jP3OTgO8XlOlH6Pe/1Qu2PEKItpuLw3gMxQZzPXZMwSA6Gkj7M0 6VEGpKxmWdBn1n9gl88X1eGWBr5fjuAO0AYqsK8r3Q7RcdnOx2qrGe0aCvz1P3I4yRKn /ndenElt0sSpM3gBOl+TYAb1+T4hBu9moFnI/ZRXXCaAbaz4c564z6BUIbb4Mk4A4vsK ZI6tTzy+G8EzzTrE/crNjKzGI90svAbgNePrtD7FJ7bHi+TkLCeq5NaRPALbpipIF+Hm eZnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:message-id:date:to:mime-version; bh=smSRZYY/PCIpmyps5t7EimA5rrltI4laUcpLxuwnauA=; b=Ilo9gYAksRnap+7bjKGshJcDEHhnqRgbPl8daXvbI5WnVE2kBtHbrqXSWd1HZOv6BC DKo+U/ZbeZzOCWpUx/8iMLluBCrlK92sgVqIWDEZZ/xUTs9L4X/gjmNw0NmBNMuRnboW dnkUOOyjpZNfAYEq7X13mgkaWTaVCn5ml9Pxg/2Pcw59wbNRM3KFQfJ9tUsOtBfuW+gp ML5UtaBImSIILNrp1XBaW5/I8y+d/WCIz90pfCrQZbnvaCv3mk7O23KCJUoHN/G7U3MC MHflE9J4ZnDeVJSJWgjaCakul2h6uR1PbaE0fjjFFuDVoBV7GLp4Dyt0TC78q8b+vUYP l9HQ== X-Gm-Message-State: ALyK8tK1Lx1DNI+xxrc6dSZs8tDu77bs+HwkWQDulkjeuPSy6uFhfaiUVbR5b5MqJfjQynb0 X-Received: by 10.25.20.95 with SMTP id k92mr2798225lfi.207.1467194402257; Wed, 29 Jun 2016 03:00:02 -0700 (PDT) Received: from [192.168.2.141] (cpe.ge-4-2-4-100.arcnqe10.dk.customer.tdc.net. [80.161.188.54]) by smtp.gmail.com with ESMTPSA id h41sm492680lji.39.2016.06.29.03.00.01 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 29 Jun 2016 03:00:01 -0700 (PDT) From: =?utf-8?Q?Niels_Kristian_Schj=C3=B8dt?= Content-Type: multipart/alternative; boundary="Apple-Mail=_CED95182-6C05-46B5-9366-FA2688DEF79B" Subject: pg_xlog dir not getting swept Message-Id: <21D0DA77-ACC3-4859-A391-03EE0B5D7E76@autouncle.com> Date: Wed, 29 Jun 2016 12:00:00 +0200 To: "pgsql-performance@postgresql.org list" Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org --Apple-Mail=_CED95182-6C05-46B5-9366-FA2688DEF79B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 About a day ago, there seems to have been some trouble in the network of = my database (postgresql 9.3).=20 I=E2=80=99m running my db with a streaming replication setup with wall = shipping.=20 I sync wal logs to a mounted networkdrive using archive_command =3D = 'rsync -a %p /mnt/wal_drive/wals/%f About a day ago, there seems to have been some trouble in the = network of my database (postgresql 9.3). 

I=E2=80=99m running my db with a = streaming replication setup with wall shipping. 

I sync wal logs to a mounted = networkdrive using archive_command =3D 'rsync -a %p /mnt/wal_drive/wals/%f = </dev/null=E2=80=99. Somehow this command was failing, leading to my = pg_xlog dir building up (590Gb). I rebooted the server, and the = archiving command seems to succeed now - however - After about an hour = of running, the pg_xlog drive has not decreased in size - I would have = expect that! I can see that lot=E2=80=99s of files get=E2=80=99s synced = to the /mnt/wal_drive/wals dir, but somehow the pg_xlog dir is not swept = (yet)? Will this happen automatically eventually, or do I need to do = something manually?

PS. I found this blog = post http://www.hivelogik.com/blog/?p=3D513, = but I=E2=80=99m unsure if it=E2=80=99s necessary and if it can = be dangerous?

Best
= --Apple-Mail=_CED95182-6C05-46B5-9366-FA2688DEF79B--