pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Merlin Moncure <mmoncure@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: Brandon Shalton <brandon@cydataservices.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: disk filling up
Date: Tue, 31 Jul 2007 12:16:38 -0400
Message-ID: <b42b73150707310916pf0bc974t9f3d3d9b647555ba@mail.gmail.com> (raw)
In-Reply-To: <6791.1185859156@sss.pgh.pa.us>
References: <009c01c7cfa0$ab526810$fc01a8c0@blaptop>
	<46A8B3EC.1090807@commandprompt.com>
	<b42b73150707270644q7957f29epdbb2b857296ed03a@mail.gmail.com>
	<6791.1185859156@sss.pgh.pa.us>

On 7/31/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Merlin Moncure" <mmoncure@gmail.com> writes:
> > third (but unlikely) possibility is there are various dropped tables,
> > etc which need to be deleted but there are stale postgresql processes
> > holding on to the fd.  This would only happen following a postmaster
> > crash or some other bizarre scenario, but i've seen it on production
> > box.
>
> Brent Reid reported something similar in bug #3483 but I'm still quite
> unclear how it'd happen in any realistic scenario.  Can you create a
> test case?

No, but I've seen it on a production 8.1 box (once).  I didn't
actually cause the problem, just cleaned it up.  It was unnoticed for
several weeks/months because the postmaster processes showed up
without a controlling tty.

My best guess is the postmaster was killed improperly out of haste
during a maintenance window, or possibly an out of disk space related
issue at an earlier point.  I never really considered that it was a
postgresql problem.

merlin



view thread (9+ messages)

Message-ID: <b42b73150707310916pf0bc974t9f3d3d9b647555ba@mail.gmail.com>
Permalink:  ../b42b73150707310916pf0bc974t9f3d3d9b647555ba@mail.gmail.com/
Also on:    postgresql.org/message-id/b42b73150707310916pf0bc974t9f3d3d9b647555ba@mail.gmail.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-performance@postgresql.org
  Cc: mmoncure@gmail.com, tgl@sss.pgh.pa.us, jd@commandprompt.com, brandon@cydataservices.com
  Subject: Re: disk filling up
  In-Reply-To: <b42b73150707310916pf0bc974t9f3d3d9b647555ba@mail.gmail.com>
  References: <009c01c7cfa0$ab526810$fc01a8c0@blaptop> <46A8B3EC.1090807@commandprompt.com> <b42b73150707270644q7957f29epdbb2b857296ed03a@mail.gmail.com> <6791.1185859156@sss.pgh.pa.us> <b42b73150707310916pf0bc974t9f3d3d9b647555ba@mail.gmail.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