Thanks, Michael, but I am absolutely convinced that whether a needed
index exists or not is absolutely one of the most run-time
consequential inputs to the query planner. Also, that page is where
people look to optimize, unlike the impenetrable wall-of-text stats
page. Please correct me if I am wro
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
stati
Michael,
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 ?
SELECT relname, seq_scan-idx_scan AS too_much_seq,
case when seq_scan-idx_scan>0 THEN 'Missing Index?' ELSE 'OK' END,
pg_rela
On Sun, Nov 24, 2019 at 09:31:58AM +, PG Doc comments form wrote:
> There needs to be a tutorial page explaining how to use pg_stat_all_tables
> to find missing indexes, or maybe just an example on monitoring-stats.html
> which is hopelessly inaccessible to a non-expert. I would have never been
