Re: Nasty VACUUM/bgwriter/segmentation bug - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Nasty VACUUM/bgwriter/segmentation bug
Date
Msg-id 1163968163.30491.30.camel@localhost.localdomain
Whole thread Raw
In response to Re: Nasty VACUUM/bgwriter/segmentation bug  (David Fetter <david@fetter.org>)
List 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





pgsql-hackers by date:

Previous
From: "Florian G. Pflug"
Date:
Subject: Re: Nasty VACUUM/bgwriter/segmentation bug
Next
From: Alvaro Herrera
Date:
Subject: Re: [GENERAL] Allowing SYSDATE to Work