Message-ID: <4D9CEA3F.5050603@wp.pl>
Date: Thu, 07 Apr 2011 00:33:35 +0200
From: Ireneusz Pluta <ipluta@wp.pl>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl;
	rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: pgsql-performance@postgresql.org
Subject: Background fsck
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hello,

I saw some recommendations from people on the net not to use background fsck when running PostgreSQL 
on FreeBSD. As I recall, these opinions were just thoughts of people which they shared with the 
community, following their bad experience caused by using background fsck. So, not coming any deeper 
with underatanding why not, I use that as a clear recommendation for myself and keep background fsck 
turned off on all my machines, regardless how much faster a server could come up after a crash.

But waiting so much time (like now) during foreground fsck of a large data filesystem after unclean 
shutdown, makes me to come to this group to ask whether I really need to avoid background fsck on a 
PostgreSQL machine? Could I hear your opinions?

Thanks

Irek.