Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YEgf1-0004nN-VR for pgsql-admin@arkaria.postgresql.org; Fri, 23 Jan 2015 16:00:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YEgf1-0005LO-EX for pgsql-admin@arkaria.postgresql.org; Fri, 23 Jan 2015 16:00:39 +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 1YEgf0-0005Iq-4D for pgsql-admin@postgresql.org; Fri, 23 Jan 2015 16:00:38 +0000 Received: from mail-yk0-x229.google.com ([2607:f8b0:4002:c07::229]) by makus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YEgex-0008TN-1g for pgsql-admin@postgresql.org; Fri, 23 Jan 2015 16:00:36 +0000 Received: by mail-yk0-f169.google.com with SMTP id 200so3569091ykr.0 for ; Fri, 23 Jan 2015 08:00:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=0GvK6HnYdurTYXXfoKfR4oq6SKtmeKbXz0iLuqbHqjg=; b=sdxRMe3QJ9YKTC5R2xtPuZxXox10sVCbLii/4Q9Nr8x4RgW+xF1FVlV5sSX5XNOLm0 sQECYhttGdEnOBz3X8s51wdSXdxTwb/Op32GOKDVbvyb1Rltrt9tHXMfgL9dLFMi+Epm HFTkiCzsGeYZCUTgrubgsNL6ebPaJwJ/TMT5hBYD42bDcxB2Mzx2yYDDQG5DpjlwodUM bNzM8gCMLmAy7gkrZsr8r8f5HC4KBqiBcvduxGuMf01RAsT/g8GLYWGXZvTNui0TvYB0 fO5MF/2CfyLWTVP5aWoJyCiouLYPWZ7iT09I+hhtL46GoJKhaVY7KTEILbOHZ9nfmdkI o71Q== X-Received: by 10.170.153.8 with SMTP id u8mr4062299ykc.52.1422028834258; Fri, 23 Jan 2015 08:00:34 -0800 (PST) Received: from [192.168.254.3] (h77.89.102.166.static.ip.windstream.net. [166.102.89.77]) by mx.google.com with ESMTPSA id d59sm1077658yho.52.2015.01.23.08.00.33 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 23 Jan 2015 08:00:33 -0800 (PST) Message-ID: <54C2701F.1020505@gmail.com> Date: Fri, 23 Jan 2015 11:00:31 -0500 From: John Scalia User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: "pgsql-admin@postgresql.org" Subject: What to do when pg_xlog directory has filled up the filesystem Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) 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 Hi all, Just curious about this issue as it has occurred on my 9.4.0 sandbox primary server. The link to the directory specified in archive_command had disappeared, 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 would not restart. I've thought about just moving some of the WAL segments temporarily to another filesystem, but which ones, oldest or newest? And is that really the best way to deal with this or what is the best way to deal with this kind of issue? -- Jay -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin