Date: Tue, 14 Nov 2017 14:26:16 -0700 (MST)
From: legrand legrand <legrand_legrand@hotmail.com>
To: pgsql-performance@postgresql.org
Message-ID: <1510694776440-0.post@n3.nabble.com>
In-Reply-To: 
 <CAER07O0_-uTR3FXjbe4qnGh2xqQWQxYVqQRjsFK7EJzVVGAdGg@mail.gmail.com>
References: 
 <CAER07O05V+3Sut=--F0Cagve81Rj7dm4fDdsUoS7NiuS+sU4hw@mail.gmail.com>
 <252cab3895894337a3a88275f423fe0b@index.de>
 <CAER07O1r-Hj4erAUBVPJfqJ1Vt-B66q73fCfjH3hBdrYo_Y1cQ@mail.gmail.com>
 <4276.1510613373@sss.pgh.pa.us>
 <CAER07O0_-uTR3FXjbe4qnGh2xqQWQxYVqQRjsFK7EJzVVGAdGg@mail.gmail.com>
Subject: Re: Query planner gaining the ability to replanning after start of
 query execution.
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

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 "corrected plan" taking into account real cardinalities was proposed
(with some advices on how to get it) it would be a great tuning adviser ;o)


--
Sent from: http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.html


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance