X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 114279DC959 for ; Mon, 2 Jan 2006 13:45:38 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 60743-07 for ; Mon, 2 Jan 2006 13:45:37 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id F37559DC8D8 for ; Mon, 2 Jan 2006 13:45:35 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k02HjTCu007231; Mon, 2 Jan 2006 12:45:29 -0500 (EST) To: "Gregory S. Williamson" cc: "Jeff Frost" , pgsql-admin@postgresql.org Subject: Re: full data disk -- any chance of recovery In-reply-to: <71E37EF6B7DCC1499CEA0316A2568328024BBD84@loki.wc.globexplorer.net> References: <71E37EF6B7DCC1499CEA0316A2568328024BBD84@loki.wc.globexplorer.net> Comments: In-reply-to "Gregory S. Williamson" message dated "Mon, 02 Jan 2006 00:39:28 -0800" Date: Mon, 02 Jan 2006 12:45:29 -0500 Message-ID: <7230.1136223929@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.059 required=5 tests=[AWL=0.059] X-Spam-Score: 0.059 X-Spam-Level: X-Archive-Number: 200601/15 X-Sequence-Number: 20103 "Gregory S. Williamson" writes: > 2006-01-02 00:30:01 LOG: could not close temporary statistics file "/data/postgres/gex_runtime/global/pgstat.tmp.1453": No space left on device > 2006-01-02 00:33:54 ERROR: could not access status of transaction 0 > DETAIL: could not write to file "/data/postgres/gex_runtime/pg_clog/0AFA" at offset 196608: No space left on device Just kill -9 all the postgres processes; everything you need should be safely down in the WAL files. You might not have to move pg_xlog --- the first thing to do is see if there are any large temp files hanging about in the pgsql_tmp subdirectories. Anything you see in there can be shot on sight once the postmaster is stopped (actually, recent versions of the postmaster will do it for you on restart, but don't remember about 7.4). Which PG release is this exactly (7.4.what)? This misbehavior reminds me of a bug that we fixed in 7.4.2. regards, tom lane