BUG #2263: corrupted pgstat.stat file

Started by Nonameabout 20 years ago2 messagesbugs
Jump to latest
#1Noname
bug1@route66.ro

The following bug has been logged online:

Bug reference: 2263
Logged by:
Email address: bug1@route66.ro
PostgreSQL version: 8.1.3
Operating system: Linux x86
Description: corrupted pgstat.stat file
Details:

Hello!

I upgraded from 8.1.2 to 8.1.3 without dumping (was not required). After
starting I got this error in the logs:

LOG: corrupted pgstat.stat file

What should I do?

Thanks!

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Noname (#1)
Re: BUG #2263: corrupted pgstat.stat file

"" <bug1@route66.ro> writes:

I upgraded from 8.1.2 to 8.1.3 without dumping (was not required). After
starting I got this error in the logs:

LOG: corrupted pgstat.stat file

What should I do?

Ignore it. We changed the format of the pgstat file between 8.1.2 and
8.1.3.

2006-01-18 15:35 tgl

* src/: backend/commands/vacuum.c, backend/postmaster/autovacuum.c,
backend/postmaster/pgstat.c, backend/storage/smgr/smgr.c,
include/pgstat.h (REL8_1_STABLE): Modify pgstats code to reduce
performance penalties from oversized stats data files: avoid
creating stats hashtable entries for tables that aren't being
touched except by vacuum/analyze, ensure that entries for dropped
tables are removed promptly, and tweak the data layout to avoid
storing useless struct padding. Also improve the performance of
pgstat_vacuum_tabstat(), and make sure that autovacuum invokes it
exactly once per autovac cycle rather than multiple times or not at
all. This should cure recent complaints about 8.1 showing much
higher stats I/O volume than was seen in 8.0. It'd still be a good
idea to revisit the design with an eye to not re-writing the entire
stats dataset every half second ... but that would be too much to
backpatch, I fear.

regards, tom lane