| From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, Hackers <pgsql-hackers(at)postgresql(dot)org>, Warren Guy <wg(at)familyhealth(dot)com(dot)au> |
| Subject: | Re: PostgreSQL and FreeBSD SoftUpdates |
| Date: | 2004-03-30 04:06:19 |
| Message-ID: | 20040330000327.A51637@ganymede.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 30 Mar 2004, Christopher Kings-Lynne wrote:
> > Right off the top of my head, it almost sounds like a file is being held
> > open after its been deleted ... we went through that with the new aspseek
> > a little while back, where 170gig just disappeared overnight, but du
> > showed hardly any disk space being used ...
> >
> > Does restarting the database server (not rebooting, just restarting the
> > postmaster) free up the disk space?
>
> No - have to reboot. That's probably because of softupdates though.
'k, *shouldn't* require a reboot ... but, what I'd try is to do what
you've thought .. disable softupdates and see if you can recreate ... if
killing off the process auto-reclaims the space fast, then it sounds like
a stale file being held open (log file being rotated improperly?) ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-03-30 04:21:05 | Re: PostgreSQL and FreeBSD SoftUpdates |
| Previous Message | Christopher Kings-Lynne | 2004-03-30 03:40:27 | Re: PostgreSQL and FreeBSD SoftUpdates |