From: Scott Marlowe <scott.marlowe@gmail.com>
To: Ireneusz Pluta <ipluta@wp.pl>
Cc: pgsql-performance@postgresql.org
Subject: Re: Background fsck
Date: Wed, 6 Apr 2011 16:48:22 -0600
Message-ID: <BANLkTim3SY4-P1xzxxfjB9BpvARfWd-Awg@mail.gmail.com> (raw)
In-Reply-To: <4D9CEA3F.5050603@wp.pl>
References: <4D9CEA3F.5050603@wp.pl>
On Wed, Apr 6, 2011 at 4:33 PM, Ireneusz Pluta <ipluta@wp.pl> wrote:
> 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?
Shouldn't a journaling file system just come back up almost immediately?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: scott.marlowe@gmail.com, ipluta@wp.pl
Subject: Re: Background fsck
In-Reply-To: <BANLkTim3SY4-P1xzxxfjB9BpvARfWd-Awg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox