Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Another issue is, some node types are not supported in outfuncs.c.
> WARNING: could not dump unrecognized node type: 911
Yeah. I think there's an unofficial policy for post-analysis parse
trees that we don't bother writing outfuncs for utility-statement
> Isn't the post-parse-analysis tree far more interesting? There's
> already debug support for printing that.
It's interesting too. But I think compraring raw parse tree and
post-parse-analysis tree is sometimes usefull to understand the source
code.
> Of course, you can call pprint() from anypl
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Very often I find it is useful to print raw parse trees for debugging
> and/or understanding PostgreSQL internals and I personally modify
> pg_parse_query() to accomplish it. If this is common among developers,
> I would like to post small patches. Opinion
Very often I find it is useful to print raw parse trees for debugging
and/or understanding PostgreSQL internals and I personally modify
pg_parse_query() to accomplish it. If this is common among developers,
I would like to post small patches. Opinion?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
--
Sent v
