From: Tom Lane <tgl@sss.pgh.pa.us>
To: Merlin Moncure <mmoncure@gmail.com>
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 01:19:16 -0400
Message-ID: <6791.1185859156@sss.pgh.pa.us> (raw)
In-Reply-To: <b42b73150707270644q7957f29epdbb2b857296ed03a@mail.gmail.com>
References: <009c01c7cfa0$ab526810$fc01a8c0@blaptop>
<46A8B3EC.1090807@commandprompt.com>
<b42b73150707270644q7957f29epdbb2b857296ed03a@mail.gmail.com>
"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?
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, mmoncure@gmail.com, jd@commandprompt.com, brandon@cydataservices.com
Subject: Re: disk filling up
In-Reply-To: <6791.1185859156@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