Re: Dubious server log messages after pg_upgrade
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org, michael@paquier.xyz
Date: 2025-03-13T01:39:41Z
Lists: pgsql-hackers
On Wed, Mar 12, 2025 at 08:41:29PM -0400, Tom Lane wrote: > The "corrupted statistics file" whine is most likely > caused by pg_upgrade copying the old system's pgstat.stat file > into the new installation --- is that a good idea? I don't believe pg_upgrade copies that file to the new cluster. At least, that would be news to me. > I have > no idea what's causing the redo LSN complaint, but it seems > like that might deserve closer investigation. pgstat_read_statsfile() emits a warning before it jumps to the section that emits the LOG. The LSN complaint seems to just be providing some context around what exactly is corrupted in pgstat.stat. Commit b860848 seems rather suspect. I've added Michael here... -- nathan
Commits
-
Revert "Add redo LSN to pgstats files"
- 5721e5453ebc 18.0 landed
-
Add redo LSN to pgstats files
- b860848232aa 18.0 cited