From: David Kerr <dmk@mr-paradox.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: "global/pgstat.stat" corrupt
Date: Fri, 22 Jun 2012 13:11:26 -0700
Message-ID: <20120622201126.GC98691@mr-paradox.net> (raw)
In-Reply-To: <17700.1340394540@sss.pgh.pa.us>
References: <20120622184632.GE94572@mr-paradox.net>
<17700.1340394540@sss.pgh.pa.us>
On Fri, Jun 22, 2012 at 03:49:00PM -0400, Tom Lane wrote:
- David Kerr <dmk@mr-paradox.net> writes:
- > I just restored a DB from a cold backup (pg_ctl stop -m fast)
-
- > When starting the DB I see:
- > LOG: corrupted statistics file "global/pgstat.stat"
-
- Is that repeatable? It wouldn't be too surprising to see this once when
- starting from a filesystem backup, if you'd managed to capture a
- partially written stats file in the backup.
hmm, possibly. it's somewhat worrysome if that file isn't written out
what else isn't getting written out.
our backups are SAN based snapshots, maybe i need to "sync" prior to the snapshot
even with the DB being down.
- > When I look at the filesystem I don't see a global/pgstat.stat file but i do see a
- > pg_stat_tmp/pgstat.stat
-
- This is normal --- global/pgstat.stat is only supposed to exist when the
- system is shut down. Transient updates are written into pg_stat_tmp/
ah ok
- > Are those stats related to pg_stats style statistics?
-
- No, this file is for the stats collection subsystem,
- http://www.postgresql.org/docs/9.1/static/monitoring-stats.html
-
- regards, tom lane
-
Oh, hmm thanks. I had looked at that before but must not have fully understood
what was going on. That's interesting!
Dave
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: dmk@mr-paradox.net, tgl@sss.pgh.pa.us
Subject: Re: "global/pgstat.stat" corrupt
In-Reply-To: <20120622201126.GC98691@mr-paradox.net>
* 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