Date: Wed, 8 Aug 2012 12:53:04 -0400
From: Wayne Cuddy <lists-pgsql@useunix.net>
To: PostgreSQL <pgsql-sql@postgresql.org>
Subject: Re: fsync debug messages in pgsql logs
Message-ID: <20120808165304.GF16371@slacker.ja10629.home>
Mail-Followup-To: PostgreSQL <pgsql-sql@postgresql.org>
References: <20120808154416.GE16371@slacker.ja10629.home>
	<12758.1344443002@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <12758.1344443002@sss.pgh.pa.us>
User-Agent: Mutt/1.4.2.3i

On Wed, Aug 08, 2012 at 12:23:22PM -0400, Tom Lane wrote:
> Wayne Cuddy <lists-pgsql@useunix.net> writes:
> > I'm seeing this in my PGSQL logs, is this something to be concerned
> > about? I know the file system it sits on is reliable and the DB appears
> > to run with fine, additionally the log indicates it's a debug message. I
> > did some google searches and didn't find much.
> > When I examine the file system file by these names to not exist.
> 
> 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?
> 
> 			regards, tom lane

It's 9.0.4. I'm frequently truncating tables but not dropping them.