From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wayne Cuddy <lists-pgsql@useunix.net>
Cc: PostgreSQL <pgsql-sql@postgresql.org>
Subject: Re: fsync debug messages in pgsql logs
Date: Wed, 08 Aug 2012 12:57:01 -0400
Message-ID: <13444.1344445021@sss.pgh.pa.us> (raw)
In-Reply-To: <20120808165304.GF16371@slacker.ja10629.home>
References: <20120808154416.GE16371@slacker.ja10629.home>
<12758.1344443002@sss.pgh.pa.us>
<20120808165304.GF16371@slacker.ja10629.home>
Wayne Cuddy <lists-pgsql@useunix.net> writes:
> On Wed, Aug 08, 2012 at 12:23:22PM -0400, Tom Lane wrote:
>> If it only complains once per file name, this is expected behavior when
>> somebody drops a table just before the checkpoint mechanism tries to
>> fsync it. (If the failure were to repeat, then it might be something
>> more interesting.) It does seem a bit odd that only fsm files are being
>> complained of, though.
>>
>> What PG version is that exactly?
> It's 9.0.4. I'm frequently truncating tables but not dropping them.
Under the hood, TRUNCATE creates a new empty table and then drops the
old one after commit. So that sounds consistent. It's still a bit odd
that all the messages are about FSM files, but maybe that has something
to do with sequence-of-operations in the DROP. Anyway, nothing to see
here AFAICT.
regards, tom lane
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, lists-pgsql@useunix.net
Subject: Re: fsync debug messages in pgsql logs
In-Reply-To: <13444.1344445021@sss.pgh.pa.us>
* 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