Checksum errors in pg_stat_database - Mailing list pgsql-hackers

From Magnus Hagander
Subject Checksum errors in pg_stat_database
Date
Msg-id CABUevExoWAKUYbqepncTFHxfzKOX+j=Ve8MZPMF+nfDTKc4WhQ@mail.gmail.com
Whole thread Raw
Responses Re: Checksum errors in pg_stat_database  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Would it make sense to add a column to pg_stat_database showing the total number of checksum errors that have occurred in a database?

It's really a ">1 means it's bad", but it's a lot easier to monitor that in the statistics views, and given how much a lot of people set their systems out to log, it's far too easy to miss individual checksum matches in the logs.

If we track it at the database level, I don't think the overhead of adding one more counter would be very high either.

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: could recovery_target_timeline=latest be the default in standbymode?
Next
From: Etsuro Fujita
Date:
Subject: Re: Query with high planning time at version 11.1 compared versions10.5 and 11.0