Re: generic explain options v3 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: generic explain options v3
Date
Msg-id 8554.1248228330@sss.pgh.pa.us
Whole thread Raw
In response to Re: generic explain options v3  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: generic explain options v3  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Jul 21, 2009 at 7:47 PM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
>> Also, I'd suggest changing the ExplainStmt struct to have a list of
>> DefElem options instead of hard-wiring the option set at that level.

> What is the advantage of that?

Fewer places to change when you add a new option; in particular, not
copyfuncs or equalfuncs.  Also, the way you are doing it is gratuitously
unlike every other command that has similar issues to deal with.
Everybody else parses their DefElem list at execution time.  I think
you should have the legacy ANALYZE and VERBOSE syntax elements generate
DefElem list members that get examined at execution.

BTW, I see that your "explain refactoring" patch is marked ready
for committer, but is it actually sane to apply it before the other
two?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Higher TOAST compression.
Next
From: Robert Haas
Date:
Subject: Re: generic explain options v3