Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bIL1h-00033I-3q for pgsql-performance@arkaria.postgresql.org; Wed, 29 Jun 2016 19:19:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bIL1g-0002r5-MZ for pgsql-performance@arkaria.postgresql.org; Wed, 29 Jun 2016 19:19:56 +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 1bIL1g-0002qw-8K for pgsql-performance@postgresql.org; Wed, 29 Jun 2016 19:19:56 +0000 Received: from mail-vk0-x231.google.com ([2607:f8b0:400c:c05::231]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bIL1d-0001Hb-8y for pgsql-performance@postgresql.org; Wed, 29 Jun 2016 19:19:55 +0000 Received: by mail-vk0-x231.google.com with SMTP id m127so19958818vkb.3 for ; Wed, 29 Jun 2016 12:19:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=7nfR3wtNUMcoQsawHGelQ366/GV0q5oxcx9EyPoV+zM=; b=cEU4rE5iP7uH14j61K/i64hBKCk4uPo6rkifsPrMr+OBusAgxqFE6FpgVdAXMVHCuR 3PUbg3S6PHsF2HE9Lvcw+yTryD22M3/cs/kxkmpKgsS2B0wAujAv50GSC5UOz0Mmsim4 rvS0tAylNsQKsiJ/RhPW1RJiUKFFi76XP9vKzqz7cfvjm+vx9JC6vKk0xhHqnkz9pIaH 1c5DWco4/FoaBYnLmKU3cjcGck+wGAkL+Tjysmk7zeegA+vxPmNEQJJnYdn0gqlwMl+y y+gOJBJlj/m1mo9/P0YNANGQgjTIIIHAUhRo4JH+3G6MYVFHT0Yd1T0JtIxItGX6yJtc D3UA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=7nfR3wtNUMcoQsawHGelQ366/GV0q5oxcx9EyPoV+zM=; b=ThdEsnALw6iwGl5HX92jlLmsV8ombIpIKYpPlKnx0FM+FRACjBnrr7OkZp1rtHGK06 pmAGhW1ftCJkzbikcCo98KYaVTLGP5DRoGa6EeRrT/gXWJurIXx3depScyb0H5xyjrN2 GHmQJqoEIzdoNp2MZAUIlws88Gow6NhOqx6qCPvE0tSk3LsdJPq2WFufF1DecC1YRYgK YqrFvrlSEHrYZKtDDiTZeR2SV9NNmDlBGfBiasJAN30S4TXAwYWKV1RUXWaCfskhMWJm Ivm+VEJWQxNw+G6lBVFbGhCYVxt72SJzr1K4u7badDKcf7K7FYwlh5JDSVZ3h4GNfwAN Z7mQ== X-Gm-Message-State: ALyK8tKOG8SLTXtIdbabB0+PDpeKffgUnnM6R/L26ENvC8nbs3uVx+LKXUU4QX6QSbXVE+5Z41L3lSCFFAIiJw== X-Received: by 10.31.10.82 with SMTP id 79mr4020516vkk.67.1467227991277; Wed, 29 Jun 2016 12:19:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.131.204 with HTTP; Wed, 29 Jun 2016 12:19:50 -0700 (PDT) In-Reply-To: <21D0DA77-ACC3-4859-A391-03EE0B5D7E76@autouncle.com> References: <21D0DA77-ACC3-4859-A391-03EE0B5D7E76@autouncle.com> From: Jeff Janes Date: Wed, 29 Jun 2016 12:19:50 -0700 Message-ID: Subject: Re: pg_xlog dir not getting swept To: =?UTF-8?Q?Niels_Kristian_Schj=C3=B8dt?= Cc: "pgsql-performance@postgresql.org list" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: -2.7 (--) 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 On Wed, Jun 29, 2016 at 3:00 AM, Niels Kristian Schj=C3=B8dt wrote: > 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 sh= ipping. > > I sync wal logs to a mounted networkdrive using archive_command =3D 'rsyn= c -a > %p /mnt/wal_drive/wals/%f 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 t= o 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? Successfully archived files are only removed by the checkpointer. The logic is quite complex and it can be very frustrating trying to predict exactly when any given file will get removed. You might want to run a few manual checkpoints to see if that cleans it up. But turn on log_checkpoints and reload the configuration first. Cheers, Jeff --=20 Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance