May I suggest the recent discussion over the dreaded NL issue ... I had some
similar ideas.
http://www.postgresql-archive.org/OLAP-reporting-queries-fall-into-nested-loops-over-seq-scans-or-other-horrible-planner-choices-td5990160.html
This could be massively useful and a huge leap in the industr
As a first step, before relaunching the query with a new plan I would be
happy to be able to get information about sql queries having wrong
estimates.
Maybe thoses SQL queries could be collected using something similar to
"auto_explain" module (tracing finished or cancelled queries).
If the "corr
