Re: making EXPLAIN extensible
От | Sami Imseih |
---|---|
Тема | Re: making EXPLAIN extensible |
Дата | |
Msg-id | CAA5RZ0vFHyK=39fOobQDZVPTfcJEAGx=cyu6vmAy6J4JZ7+SKg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: making EXPLAIN extensible (Andrei Lepikhov <lepihov@gmail.com>) |
Ответы |
Re: making EXPLAIN extensible
Re: making EXPLAIN extensible |
Список | 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 по дате отправления: