Postgres Pro
Downloads
Home   >   mailing lists

Re: explain.c: why trace PlanState and Plan trees separately? - Mailing list pgsql-hackers

From Yeb Havinga
Subject Re: explain.c: why trace PlanState and Plan trees separately?
Date
Msg-id 4C3C28DD.1060702@gmail.com
Whole thread Raw
In response to explain.c: why trace PlanState and Plan trees separately?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: explain.c: why trace PlanState and Plan trees separately?
List pgsql-hackers
Tree view 
Tom Lane wrote:
> The reason I'm on about this at the moment is that I think I see how to
> get ruleutils to print PARAM_EXEC Params as the referenced expression
> rather than $N ...
Wouldn't this obfuscate the plan more than printing subplan arguments at 
the call site?

regards,
Yeb Havinga

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: patch (for 9.1) string functions
Next
From: Stephen Frost
Date:
Subject: Re: dblink regression failure in HEAD