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 9FB659DCA16 for ; Wed, 4 Jan 2006 00:10:09 -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 19016-03 for ; Wed, 4 Jan 2006 00:10:07 -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 C81D39DCA30 for ; Wed, 4 Jan 2006 00:10:06 -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 k044A2nP028960; Tue, 3 Jan 2006 23:10:02 -0500 (EST) To: "Jim C. Nasby" cc: "Gregory S. Williamson" , Tomaz Borstnar , pgsql-admin@postgresql.org Subject: Re: full data disk -- any chance of recovery In-reply-to: <20060104013511.GG82560@pervasive.com> References: <71E37EF6B7DCC1499CEA0316A2568328024BBD9F@loki.wc.globexplorer.net> <20060104013511.GG82560@pervasive.com> Comments: In-reply-to "Jim C. Nasby" message dated "Tue, 03 Jan 2006 19:35:11 -0600" Date: Tue, 03 Jan 2006 23:10:02 -0500 Message-ID: <28959.1136347802@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.065 required=5 tests=[AWL=0.065] X-Spam-Score: 0.065 X-Spam-Level: X-Archive-Number: 200601/36 X-Sequence-Number: 20124 "Jim C. Nasby" writes: > On Tue, Jan 03, 2006 at 05:17:45PM -0800, Gregory S. Williamson wrote: >> I went sleuthing and found some core files in the ./base/13860299 directory. Deleteing those freed up some gigabytes of space (each core was 1-2 gigs). > Might want to turn off dumping of core files; I believe man ulimit is > the place to look. Actually, as a developer I would've first wanted to look into the core files and try to see why they showed up in the first place. A gdb stack trace would often tell something useful (... if not to you, then to someone on the -hackers list ...). Cleaning up after a problem is fine, but don't destroy the evidence until you've learned as much as you can towards preventing the problem from happening again. I spend a remarkably large fraction of my time advising people to enable core-dumping on platforms that disable it by default, so you'll certainly not ever see me advising anyone to turn it off on a platform where it is default ;-) Having said all that, +1 to the point about staying up-to-date in whichever PG release series you are using. We do not spend time on making dot-releases because we have nothing to do on a Saturday afternoon ... an update is put out because it fixes one or more pretty serious bugs. Sure, there is some risk of a regression in a dot-release, but it's small. As best I recall at the moment, we've had only one or two regressions in dot-releases in the eight or so years I've been around the project. regards, tom lane