Skip site navigation (1) Skip section navigation (2)

Re: disk filling up

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Brandon Shalton" <brandon(at)cydataservices(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: disk filling up
Date: 2007-07-31 05:19:16
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
"Merlin Moncure" <mmoncure(at)gmail(dot)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

In response to


pgsql-performance by date

Next:From: Henrik ZagerholmDate: 2007-07-31 08:23:38
Subject: Seq scan on join table despite index and high statistics
Previous:From: Decibel!Date: 2007-07-31 01:46:37
Subject: Re: Vacuum looping?

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group