Skip site navigation (1) Skip section navigation (2)

Re: fsync debug messages in pgsql logs

From: Wayne Cuddy <lists-pgsql(at)useunix(dot)net>
To: PostgreSQL <pgsql-sql(at)postgresql(dot)org>
Subject: Re: fsync debug messages in pgsql logs
Date: 2012-08-08 17:11:56
Message-ID: 20120808171156.GG16371@slacker.ja10629.home (view raw, whole thread or download thread mbox)
Lists: pgsql-sql
Ok, I'll keep an eye on it but I'm not so worried now.

Thanks Tom.

On Wed, Aug 08, 2012 at 12:57:01PM -0400, Tom Lane wrote:
> Wayne Cuddy <lists-pgsql(at)useunix(dot)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
> -- 
> Sent via pgsql-sql mailing list (pgsql-sql(at)postgresql(dot)org)
> To make changes to your subscription:

In response to

pgsql-sql by date

Next:From: amit sehasDate: 2012-08-14 16:54:48
Subject: Indexing question
Previous:From: Tom LaneDate: 2012-08-08 16:57:01
Subject: Re: fsync debug messages in pgsql logs

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group