Re: explain.c: why trace PlanState and Plan trees separately?

From: Yeb Havinga <yebhavinga(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: explain.c: why trace PlanState and Plan trees separately?
Date: 2010-07-13 08:50:37
Message-ID: 4C3C28DD.1060702@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2010-07-13 11:05:21 Re: dblink regression failure in HEAD
Previous Message Pavel Stehule 2010-07-13 07:54:30 Re: patch (for 9.1) string functions