Re: making EXPLAIN extensible - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: making EXPLAIN extensible
Date
Msg-id CAA5RZ0vFHyK=39fOobQDZVPTfcJEAGx=cyu6vmAy6J4JZ7+SKg@mail.gmail.com
Whole thread Raw
In response to Re: making EXPLAIN extensible  (Andrei Lepikhov <lepihov@gmail.com>)
Responses Re: making EXPLAIN extensible
Re: making EXPLAIN extensible
List pgsql-hackers
> Why do you think this hook is not redundant?
what is it redundant with?

> It would be better to add the parameter "type: EXPLAIN_ONLY |
> ANALYZE_ONLY | BOTH" to the RegisterExtensionExplainOption() routine.
> This value will be saved inside the ExplainExtensionOption structure and
> processed by the core inside the ParseExplainOptionList.

hmm, IIUC, what you are describing is flag that will be limited to
only check if an option can be used with EXPLAIN_ONLY, ANALYZE_ONLY
or both. But what about if I have a case to check against between other
extension options? let's say ExtensionAOptionA and ExtensionAoptionB.
How would that work with the way you are suggesting?

--
Sami Imseih
Amazon Web Services (AWS)



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: pg_trgm comparison bug on cross-architecture replication due to different char implementation
Next
From: Tom Lane
Date:
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER