Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id D55BD7ACC83 for ; Wed, 8 Aug 2012 13:57:17 -0300 (ADT) Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Sz9ZK-00010W-M0 for pgsql-sql@postgresql.org; Wed, 08 Aug 2012 16:57:17 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q78Gv1Ia013445; Wed, 8 Aug 2012 12:57:01 -0400 (EDT) From: Tom Lane To: Wayne Cuddy cc: PostgreSQL Subject: Re: fsync debug messages in pgsql logs 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> Comments: In-reply-to Wayne Cuddy message dated "Wed, 08 Aug 2012 12:53:04 -0400" Date: Wed, 08 Aug 2012 12:57:01 -0400 Message-ID: <13444.1344445021@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201208/12 X-Sequence-Number: 36783 Wayne Cuddy 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