Re: [HACKERS] debugging tools inside postgres

2011-06-25 Thread Martijn van Oosterhout
On Fri, Jun 24, 2011 at 02:35:08PM +0800, HuangQi wrote: Hi, I'm trying to debug a modification for the query planner. But I found it seems the data structure of my planned query is incorrect. I was trying to print out the data structure by use the p command in gdb which is quite

Re: [HACKERS] debugging tools inside postgres

2011-06-24 Thread Shigeru Hanada
(2011/06/24 15:35), HuangQi wrote: Hi, I'm trying to debug a modification for the query planner. But I found it seems the data structure of my planned query is incorrect. I was trying to print out the data structure by use the p command in gdb which is quite inconvenient and takes time.

Re: [HACKERS] debugging tools inside postgres

2011-06-24 Thread HuangQi
2011/6/24 Shigeru Hanada shigeru.han...@gmail.com (2011/06/24 15:35), HuangQi wrote: Hi, I'm trying to debug a modification for the query planner. But I found it seems the data structure of my planned query is incorrect. I was trying to print out the data structure by use the p

Re: [HACKERS] debugging tools inside postgres

2011-06-24 Thread Shigeru Hanada
(2011/06/24 19:14), HuangQi wrote: 2011/6/24 Shigeru Hanadashigeru.han...@gmail.com (2011/06/24 15:35), HuangQi wrote: ex) elog(DEBUG1, %s, nodeToString(plan)); Hi, I don't know why but when I am debugging the query evaluation, the elog function can not output to shell.

Re: [HACKERS] debugging tools inside postgres

2011-06-24 Thread Tom Lane
Shigeru Hanada shigeru.han...@gmail.com writes: (2011/06/24 15:35), HuangQi wrote: I'm trying to debug a modification for the query planner. But I found it seems the data structure of my planned query is incorrect. I was trying to print out the data structure by use the p command in gdb which

Re: [HACKERS] debugging tools inside postgres

2011-06-24 Thread HuangQi
On 24 June 2011 23:21, Tom Lane t...@sss.pgh.pa.us wrote: Shigeru Hanada shigeru.han...@gmail.com writes: (2011/06/24 15:35), HuangQi wrote: I'm trying to debug a modification for the query planner. But I found it seems the data structure of my planned query is incorrect. I was trying to