From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: Gregory S. Williamson <gsw@globexplorer.com>
Cc: Tomaz Borstnar <tomaz.borstnar@over.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: full data disk -- any chance of recovery
Date: Tue, 03 Jan 2006 23:10:02 -0500
Message-ID: <28959.1136347802@sss.pgh.pa.us> (raw)
In-Reply-To: <20060104013511.GG82560@pervasive.com>
References: <71E37EF6B7DCC1499CEA0316A2568328024BBD9F@loki.wc.globexplorer.net>
<20060104013511.GG82560@pervasive.com>
"Jim C. Nasby" <jnasby@pervasive.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, jnasby@pervasive.com, gsw@globexplorer.com, tomaz.borstnar@over.net
Subject: Re: full data disk -- any chance of recovery
In-Reply-To: <28959.1136347802@sss.pgh.pa.us>
References: <71E37EF6B7DCC1499CEA0316A2568328024BBD9F@loki.wc.globexplorer.net> <20060104013511.GG82560@pervasive.com> <28959.1136347802@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox