Re: making EXPLAIN extensible - Mailing list pgsql-hackers

From Robert Haas
Subject Re: making EXPLAIN extensible
Date
Msg-id CA+TgmobMQqqTd13BCTyLQf+vB5DKAnpg9LbeHHhkNaENqusKQQ@mail.gmail.com
Whole thread Raw
In response to Re: making EXPLAIN extensible  (Andrei Lepikhov <lepihov@gmail.com>)
List pgsql-hackers
On Thu, May 22, 2025 at 10:29 AM Andrei Lepikhov <lepihov@gmail.com> wrote:
> > I don't think this is really true. It's just standard identifier
> > handling. You can have options with upper-case names if you quote
> > them.
> Sorry for my language. I meant that when you call function
> RegisterExtensionExplainOption(), it make sense if you write parameter
> `option_name` as "debug" or "deBug". On the user side
> case-insensitiveness works correctly, of course. Not sure about side
> effects if one extension will call this routine with "Debug" parameter
> and another one - "debuG".

I guess my point is that this works just like other cases where SQL
identifiers are accessible in C code: they're normally lower-case but
they don't have to be if the user quoted them. I don't think it's
worth adding a comment about that general behavior to this specific
bit of code.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: Relstats after VACUUM FULL and CLUSTER
Next
From: Nathan Bossart
Date:
Subject: Re: Statistics Import and Export