Re: Nasty VACUUM/bgwriter/segmentation bug

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: "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 19:28:14
Message-ID: 200611191128.14845.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?).

--
Josh Berkus
PostgreSQL @ Sun
San Francisco

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2006-11-19 20:01:15 Re: Nasty VACUUM/bgwriter/segmentation bug
Previous Message Heikki Linnakangas 2006-11-19 18:33:05 Re: Nasty VACUUM/bgwriter/segmentation bug