From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Nasty VACUUM/bgwriter/segmentation bug |
Date: | 2006-11-19 20:29:23 |
Message-ID: | 1163968163.30491.30.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 2006-11-19 at 12:03 -0800, David Fetter wrote:
> On Sun, Nov 19, 2006 at 12:01:15PM -0800, Joshua D. Drake wrote:
> > On Sun, 2006-11-19 at 11:28 -0800, Josh Berkus wrote:
> > > Tom,
> > >
> > > > Let's go with the easy fix. With regular 1GB segment size,
> > > > having a few empty files in the data directory isn't going to
> > > > hurt anyone.
> > >
> > > No, but it will confuse DBAs ("What the heck are all these 0B
> > > files?"). Maybe we should add code to VACUUM to look for these
> > > empty file segments and unlink them if they haven't been touched
> > > in a while (say, a day?).
> >
> > I don't buy this argument. A smart DBA isn't going to do any such
> > thing. If you go around deleting unknown files you deserve
> > everything you get. Especially if you are in the middle of a
> > PostgreSQL cluster tree.
>
> A mention in the README in that directory wouldn't hurt, tho.
Definitely :)
Sincerely,
Joshua D. Drake
>
> Cheers,
> D
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2006-11-19 22:37:53 | Re: [GENERAL] Allowing SYSDATE to Work |
Previous Message | Florian G. Pflug | 2006-11-19 20:28:49 | Re: Nasty VACUUM/bgwriter/segmentation bug |