Re: Higher level questions around shared memory stats

[Peter Eisentraut]

On 29.03.22 23:01, Andres Freund wrote:
I think what's actually most important here is the error reporting. We need
to make it clear, at least via log messages, that something bad has
happened.
The message currently (on HEAD, but similarly on the path) is:
                                ereport(pgStatRunningInCollector ? LOG : 
WARNING,
                                                (errmsg("corrupted statistics file 
\"%s\"",
                                                                statfile)));

Corrupted how?  How does it know?  Is there a checksum, was the file the 
wrong length, what happened?  I think this could use more detail.