| From: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Sami Imseih <samimseih(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: making EXPLAIN extensible |
| Date: | 2025-03-27 21:34:31 |
| Message-ID: | 41a344e3-ffb1-4296-8ba7-801f1e9642e5@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/26/25 19:09, Robert Haas wrote:
> On Sat, Mar 22, 2025 at 12:10 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> I'm not going
>> to insist on shipping this if I'm the ONLY one who would ever get any
>> use out of it, but I doubt that's the case.
>
> Hearing no other votes against this, I have committed it, but now I
> wonder if that is going to break the buildfarm, because I just noticed
> that the changes I made in v9 seem not to have resolved the problem
> with debug_parallel_query, for reasons I do not yet understand.
> Investigating...
I’m afraid to sound like a bore, but I think pg_overexplain should
include a call into the hook call chain (see attachment). Who knows,
maybe this extension will be used someday in production?
--
regards, Andrei Lepikhov
| Attachment | Content-Type | Size |
|---|---|---|
| v0-0001-Add-into-pg_overexplain-example-on-a-hook-call-ch.patch | text/x-patch | 1.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-03-27 21:50:48 | Re: Remove restrictions in recursive query |
| Previous Message | Renan Alves Fonseca | 2025-03-27 21:21:32 | Re: Remove restrictions in recursive query |