Re: debugging tools inside postgres - Mailing list pgsql-hackers

From HuangQi
Subject Re: debugging tools inside postgres
Date
Msg-id BANLkTi=Gj9c2BU62usG5G8sv9tNqxvuSvw@mail.gmail.com
Whole thread Raw
In response to Re: debugging tools inside postgres  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
<div class="gmail_quote">On 24 June 2011 23:21, Tom Lane <span dir="ltr"><<a
href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>></span>wrote:<br /><blockquote class="gmail_quote"
style="margin:00 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">Shigeru Hanada <<a
href="mailto:shigeru.hanada@gmail.com">shigeru.hanada@gmail.com</a>>writes:<br /> > (2011/06/24 15:35), HuangQi
wrote:<br/></div><div class="im">>> I'm trying to debug a modification for the query planner. But I found it<br
/>>> seems the data structure of my planned query is incorrect. I was trying to<br /> >> print out the data
structureby use the "p" command in gdb which is quite<br /> >> inconvenient and takes time. May I know is there
anyembedded function in<br /> >> postgres to print out the node data structures, or any other plan related<br />
>>data structures? Thanks.<br /><br /> > I think nodeToString() would help.<br /><br /></div>For interactive
usein gdb, I generally do<br /><br />        call pprint(..node pointer..)<br /><br /> which prints to the postmaster
log.<br/><br />                        regards, tom lane<br /></blockquote></div><br /><br clear="all" />Thanks, Tom,
thiscall pprint() works very nice.<br />-- <br />Best Regards<br />Huang Qi Victor<br /> 

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: debugging tools inside postgres
Next
From: Robert Haas
Date:
Subject: Re: Re: starting to review the Extend NOT NULL representation to pg_constraint patch