From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ExplainOneQuery_hook ignored for EXPLAIN EXECUTE |
Date: | 2017-12-05 02:43:15 |
Message-ID: | CAM-w4HP7Jh4wRcG10CLYJxX5aSLoUbZ0bgkaMUeRaTbx=xXP0w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 13 November 2016 at 22:31, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> On 2016-11-13 17:20:05 -0500, Tom Lane wrote:
>>> Why do you care? It's a pretty specialized hook.
>
>> Citus currently uses it to output additional information for distributed
>> queries. I suspect we'll instead, for now, have to intercept EXPLAIN as
>> a whole then :( (moving to custom plans unfortunately is still a bit off
>> unfortunately).
>
> Seems like you might want a hook further down then, perhaps at
> ExplainPrintPlan.
Fwiw I've found myself wishing for the same hook. I would like to add
a feature for pg_stat_statements to make some easy way to look up the
queryid for a given query. It seems like having it annotate EXPLAIN
output would be ideal.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2017-12-05 03:15:56 | Re: REPLICA IDENTITY FULL |
Previous Message | Tom Lane | 2017-12-05 02:38:33 | Re: Error handling (or lack of it) in RemovePgTempFilesInDir |