Re: EXEC_EVALDEBUG debugging broken? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: EXEC_EVALDEBUG debugging broken?
Date
Msg-id 10933.1185294356@sss.pgh.pa.us
Whole thread Raw
In response to Re: EXEC_EVALDEBUG debugging broken?  (peter.trautmeier@gmx.de)
Responses Re: EXEC_EVALDEBUG debugging broken?  (peter.trautmeier@gmx.de)
List pgsql-hackers
peter.trautmeier@gmx.de writes:
> Interesting, what do you mean by Plan trees are 'read only' now? Is it the distinction between Plan trees and their
correspondingPlanState nodes that indicate the 'read only' behaviour and the 'writeable' state of the Plan,
respectively,that was introduced at that time?
 

Yeah, exactly.  ExecInitExpr builds an ExprState tree that mirrors the
structure of the Expr tree but contains all the run-time-variable data.
This tree is what's now being passed to ExecQual.

The problem is that outfuncs.c knows about all the Expr node types and
none of the ExprState types, there being no need to dump the latter in
normal use.  There is a valid argument that we ought to support dumping
PlanState and ExprState trees for debugging purposes, but it just seems
like more maintenance effort than it's worth ...

> (Is there a way do get this type info with gdb's help?)

"p *(Node *) ptr" ought to do it.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: strange buildfarm failure on lionfish
Next
From: peter.trautmeier@gmx.de
Date:
Subject: Design: Escort info from WHERE clause to executor?