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

From Heikki Linnakangas
Subject Re: Nasty VACUUM/bgwriter/segmentation bug
Date
Msg-id 4560A361.5090003@enterprisedb.com
Whole thread Raw
In response to Nasty VACUUM/bgwriter/segmentation bug  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Nasty VACUUM/bgwriter/segmentation bug
List pgsql-hackers
Tom Lane wrote:
> I think that the easiest fix might be to not remove no-longer-used
> segment files during a truncate, but simply reduce them to zero size
> rather than delete them.  Then any open file pointers aren't
> invalidated.  The only alternative I can see is to invent some new
> signaling mechanism to force closure of open files, but that seems
> ugly, complex, and perhaps subject to race conditions.
> 
> Thoughts?

Ouch.

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.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: "Bort, Paul"
Date:
Subject: Re: Nasty VACUUM/bgwriter/segmentation bug
Next
From: Josh Berkus
Date:
Subject: Re: Nasty VACUUM/bgwriter/segmentation bug