From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | "Gregory S(dot) Williamson" <gsw(at)globexplorer(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomaz Borstnar <tomaz(dot)borstnar(at)over(dot)net>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: full data disk -- any chance of recovery |
Date: | 2006-01-04 01:35:11 |
Message-ID: | 20060104013511.GG82560@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, Jan 03, 2006 at 05:17:45PM -0800, Gregory S. Williamson wrote:
> FWIW,
>
> I can at least report the resolution of the original problem.
>
> 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.
> a) upgrade to current revisions whenever possible -- old software is a hand grenade waiting to go off.
Well, at least in the case of PostgreSQL, it's generally not critical to
upgrade major (x.y) versions quickly. But you often do want to upgrade
minor (x.y.z) versions, as they often contain bug fixes. But 7.4.x is
getting pretty old.
> c) don't run out of disk space (duh)
There have actually been fixes to make it less of an issue when you do
run out of disk space. See item a. :)
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-01-04 04:10:02 | Re: full data disk -- any chance of recovery |
Previous Message | Jeff Frost | 2006-01-04 01:18:50 | Re: full data disk -- any chance of recovery |