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 E2F2C9DCAD0 for ; Thu, 5 Jan 2006 01:56:55 -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 95097-09 for ; Thu, 5 Jan 2006 01:56:55 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by postgresql.org (Postfix) with ESMTP id EBB5B9DCA8C for ; Thu, 5 Jan 2006 01:56:53 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id k055uqiu030726 for ; Thu, 5 Jan 2006 05:56:52 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id k055hKBY029473 for pgsql-admin@postgresql.org; Thu, 5 Jan 2006 05:43:20 GMT (envelope-from news) From: Tomaz Borstnar X-Newsgroups: pgsql.admin Subject: Re: full data disk -- any chance of recovery Date: Thu, 05 Jan 2006 06:43:09 +0100 Organization: Hub.Org Networking Services Lines: 18 Message-ID: References: <71E37EF6B7DCC1499CEA0316A2568328024BBD84@loki.wc.globexplorer.net> <18812.1136313493@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@news.hub.org User-Agent: Thunderbird 1.5 (Windows/20051201) In-Reply-To: <18812.1136313493@sss.pgh.pa.us> To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=-1.44 required=5 tests=[ALL_TRUSTED=-1.44] X-Spam-Score: -1.44 X-Spam-Level: X-Archive-Number: 200601/62 X-Sequence-Number: 20150 Tom Lane pravi: > Tomaz Borstnar writes: >> Jeff Frost pravi: >>> Seems like you're going to have to kill -9. > >> Yeah, this is bad :( Seems like kill -9 is needed when disk is full. Tested on *BSD jails. > > With what PG version? 8.0.x for sure. > And what behavior did you see exactly? Postgresql was running inside jail. All was fine until partition filled up and at this point kill -9 was the only option to stop postgresql in jail. It said about stopping by administrative command, but it did not exit - kill -9 was the only solution without rebooting. Tomaž