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

In response to

• how to watch parse/plan trees at 2002-01-02 13:25:10 from Hannu Krosing

pgsql-hackers by date

Next:	From: Holger Krug	Date: 2002-01-02 17:03:41
	Subject: Re: Feature proposal: generalizing deferred trigger events
Previous:	From: Tom Lane	Date: 2002-01-02 16:35:08
	Subject: Re: datetime error?