| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Checksum errors in pg_stat_database |
| Date: | 2019-01-11 10:20:35 |
| Message-ID: | CABUevExoWAKUYbqepncTFHxfzKOX+j=Ve8MZPMF+nfDTKc4WhQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2019-01-11 11:04:40 | Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 |
| Previous Message | Peter Eisentraut | 2019-01-11 10:17:48 | Re: could recovery_target_timeline=latest be the default in standby mode? |