Re: Nasty VACUUM/bgwriter/segmentation bug

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: Nasty VACUUM/bgwriter/segmentation bug
Дата
Msg-id 4560A361.5090003@enterprisedb.com
обсуждение исходный текст
Ответ на Nasty VACUUM/bgwriter/segmentation bug  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Nasty VACUUM/bgwriter/segmentation bug
Список 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 по дате отправления:

Предыдущее
От: "Bort, Paul"
Дата:
Сообщение: Re: Nasty VACUUM/bgwriter/segmentation bug
Следующее
От: Josh Berkus
Дата:
Сообщение: Re: Nasty VACUUM/bgwriter/segmentation bug