| From: | Rafsun Masud <rafsun(dot)masud(dot)99(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: printing raw parse tree |
| Date: | 2024-01-08 20:06:22 |
| Message-ID: | 265a014f-ad96-4a16-9282-b99c1d08631b@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Yeah. I think there's an unofficial policy for post-analysis parse
> trees that we don't bother writing outfuncs for utility-statement
> nodes (there are too many of 'em and they're not interesting enough)
> but anything that can appear in or under DML commands should be
> dumpable. I'd favor the equivalent rule for raw parse trees --- if
> we're missing anything DML-ish let's add it.
>
> regards, tom lane
Is there a way to make debug_print_parse output in JSON format?
--
Regards,
Rafsun Masud
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-01-08 20:10:33 | Re: Emit fewer vacuum records by reaping removable tuples during pruning |
| Previous Message | Alexander Lakhin | 2024-01-08 20:00:01 | Re: Removing unneeded self joins |