pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Gregory S. Williamson <gsw@globexplorer.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tomaz Borstnar <tomaz.borstnar@over.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: full data disk -- any chance of recovery
Date: Tue, 3 Jan 2006 19:35:11 -0600
Message-ID: <20060104013511.GG82560@pervasive.com> (raw)
In-Reply-To: <71E37EF6B7DCC1499CEA0316A2568328024BBD9F@loki.wc.globexplorer.net>
References: <71E37EF6B7DCC1499CEA0316A2568328024BBD9F@loki.wc.globexplorer.net>

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@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (21+ messages)  latest in thread

Message-ID: <20060104013511.GG82560@pervasive.com>
Permalink:  ../20060104013511.GG82560@pervasive.com/
Also on:    postgresql.org/message-id/20060104013511.GG82560@pervasive.com

 · 

reply

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: jnasby@pervasive.com, gsw@globexplorer.com, tgl@sss.pgh.pa.us, tomaz.borstnar@over.net
  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>

* 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