From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
Cc: | Jean-Christophe BOGGIO <postgresql(at)thefreecat(dot)org>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Why isn't PG using an index-only scan? |
Date: | 2025-09-18 11:35:34 |
Message-ID: | CAApHDvodjGfmN8_na70Bn5OVPO1-gQo64s6n=HUxqnUUQFsUZA@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, 18 Sept 2025 at 19:55, Andrei Lepikhov <lepihov(at)gmail(dot)com> wrote:
> Imagine if we had a hook within the ExecProcNode. In that scenario, we
> could create a trivial extension that would stop the query after, let's
> say, 10 minutes of execution and display the current state. This would
> give us more reliable data on estimation and the state of the plan tree.
I recall something along those lines existing once in the extension
world. Or maybe just from a previous employer. I don't recall many of
the details. Maybe something like a function you pass an SQL string
and if you cancelled the query it reported the EXPLAIN ANALYZE done so
far. I assume it must have done something like LOG it as it couldn't
have shown the EXPLAIN as query results on cancel.
David
From | Date | Subject | |
---|---|---|---|
Next Message | Andrei Lepikhov | 2025-09-18 11:55:02 | Re: Why isn't PG using an index-only scan? |
Previous Message | David Rowley | 2025-09-18 11:32:01 | Re: Why isn't PG using an index-only scan? |