Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YEhAq-0005x8-7K for pgsql-admin@arkaria.postgresql.org; Fri, 23 Jan 2015 16:33:32 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YEhAp-0007AZ-MF for pgsql-admin@arkaria.postgresql.org; Fri, 23 Jan 2015 16:33:31 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YEhAo-00077l-4W for pgsql-admin@postgresql.org; Fri, 23 Jan 2015 16:33:30 +0000 Received: from smtp106.ord1c.emailsrvr.com ([108.166.43.106]) by makus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YEhAl-0000b3-1w for pgsql-admin@postgresql.org; Fri, 23 Jan 2015 16:33:28 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 0C8C880265; Fri, 23 Jan 2015 11:33:23 -0500 (EST) X-Virus-Scanned: OK Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: jeff.frost-AT-pgexperts.com) with ESMTPSA id 0C34880422; Fri, 23 Jan 2015 11:33:22 -0500 (EST) X-Sender-Id: jeff.frost@pgexperts.com Received: from [10.143.1.72] ([UNAVAILABLE]. [166.170.36.147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.4.2); Fri, 23 Jan 2015 16:33:23 GMT Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: What to do when pg_xlog directory has filled up the filesystem From: Jeff Frost X-Mailer: iPhone Mail (12B440) In-Reply-To: <54C2701F.1020505@gmail.com> Date: Fri, 23 Jan 2015 08:33:21 -0800 Cc: "pgsql-admin@postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: <08DE332B-60AE-4B3D-8D82-7EEBDDCCB6CF@pgexperts.com> References: <54C2701F.1020505@gmail.com> To: John Scalia X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org > On Jan 23, 2015, at 08:00, John Scalia wrote: >=20 > Hi all, >=20 > Just curious about this issue as it has occurred on my 9.4.0 sandbox prim= ary server. The link to the directory specified in archive_command had disa= ppeared, so the command specified in archive_command kept failing overnight= . This resulted in many WAL segments piling up in the pg_xlog directory and= a bunch of .ready files appearing in the pg_xlog/archive.status = directory. The filesystem had reached 100% full so the database quit and wo= uld not restart. I've thought about just moving some of the WAL segments te= mporarily to another filesystem, but which ones, oldest or newest? And is t= hat really the best way to deal with this or what is the best way to deal w= ith this kind of issue? If you are on ext4, you can just: tune2fs -m 0 /dev/sda1 Or whatever device you're talking about.=20 That will reset the reserved space to 0. Then you can start up PostgreSQL and let it do the archiving. After it's do= ne: tune2fs -m 5 /dev/sda1 To put it back to the default.=20 --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin