From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | how to watch parse/plan trees |
Date: | 2002-01-02 13:25:10 |
Message-ID: | 3C330A36.A287A0AA@tm.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
How do you people look at various trees and lists when debugging them ?
Do you
1. use functions from nodes/print.c to print out tree snapshots
2. run the backend under visual debugger (like DDD) and look at things
there
3. memorize everything in binary and work on raw memory image from
/proc/core ;)
4. use some other method
I am currently working on understanding enough of the parse/plan/execute
process to make up a good plan for implementing WITH RECURSIVE ...
SELECT ...
and perhaps GROUP BY ROLLUP(a,b,c) from SQL99 spec and I'm not
proceeding
as fast as I'd like ;-p
Also could anyone recommend any tools for debugging gram.y or is this
also
done mostly by hand even for large grammars ?
------------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2002-01-02 13:40:21 | Re: Duplicate-key-detection failure case found in btree |
Previous Message | Karel Zak | 2002-01-02 11:03:24 | datetime error? |