Re: monitoring-stats.html is too impenetrable

Michael Paquier <[email protected]> Fri, 6 Dec 2019 12:04:45 +0900

Newsgroups	gmane.comp.db.postgresql.devel.documentation
Message-ID	<[email protected]>

On Wed, Dec 04, 2019 at 03:29:55AM -0800, James Salsman wrote:
> Thank you for your thoughtful reply. This might be much easier:
> 
> How about adding another example to
> https://www.postgresql.org/docs/11/planner-stats.html ?

Not sure I see the parallel here.  This page talks about planner
statistics, and yours about being able to find missing indexes because
of incorrect stats.

> SELECT relname, seq_scan-idx_scan AS too_much_seq,
>    case when seq_scan-idx_scan>0 THEN 'Missing Index?' ELSE 'OK' END,
>    pg_relation_size(relid::regclass) AS rel_size, seq_scan, idx_scan
> FROM pg_stat_all_tables
> WHERE schemaname='public' AND pg_relation_size(relid::regclass)>80000
> ORDER BY too_much_seq DESC;

Again.  this is a bit more complex than that.
--
Michael

signature.asc (application/pgp-signature, 833 B)