Re: making EXPLAIN extensible - Mailing list pgsql-hackers

From Andrei Lepikhov
Subject Re: making EXPLAIN extensible
Date
Msg-id 25642340-0f04-4a19-a332-e6567dd436f6@gmail.com
Whole thread Raw
In response to Re: making EXPLAIN extensible  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 28/3/2025 14:09, Robert Haas wrote:
> On Thu, Mar 27, 2025 at 5:34 PM Andrei Lepikhov <lepihov@gmail.com> wrote:
>> 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?
> 
> Oh, bother, that was a silly mistake on my part. Thanks, committed.
I have one additional proposal.

I currently use this interface and have noticed that the parameter 
`option_name` in the RegisterExtensionExplainOption routine is 
case-sensitive. Since SQL treats our extended options as 
case-insensitive, it would be beneficial to either add a comment 
clarifying this behavior or forcedly convert incoming text constant to 
lowercase.

-- 
regards, Andrei Lepikhov



pgsql-hackers by date:

Previous
From: Tanin Na Nakorn
Date:
Subject: pg_dump to support "on conflict do update"
Next
From: "David G. Johnston"
Date:
Subject: Re: pg_dump to support "on conflict do update"