From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Hannu Krosing <hannu(at)tm(dot)ee> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: how to watch parse/plan trees |
Date: | 2002-01-02 16:41:08 |
Message-ID: | 4598.1009989668@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hannu Krosing <hannu(at)tm(dot)ee> writes:
> How do you people look at various trees and lists when debugging them ?
I tend to start psql with PGOPTIONS="-d2" and then look at the
prettyprinted trees in the postmaster log.
If you have a bug that prevents you from getting as far as the parsetree
dump, however, gdb is probably the only way.
> Also could anyone recommend any tools for debugging gram.y or is this
> also done mostly by hand even for large grammars ?
Once you've got rid of any shift/reduce or reduce/reduce conflicts
(bison -v output is helpful for that), I find that the grammar itself
seldom has any surprising behaviors that you need to use a debugger
to follow.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Holger Krug | 2002-01-02 17:03:41 | Re: Feature proposal: generalizing deferred trigger events |
Previous Message | Tom Lane | 2002-01-02 16:35:08 | Re: datetime error? |