| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Allow to log raw parse tree. |
| Date: | 2025-09-06 00:52:02 |
| Message-ID: | aLuFskCZhvdqDrtt@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Fri, Sep 05, 2025 at 10:52:55PM +0000, Tatsuo Ishii wrote:
> Allow to log raw parse tree.
>
> This commit allows to log the raw parse tree in the same way we
> currently log the parse tree, rewritten tree, and plan tree.
>
> To avoid unnecessary log noise for users not interested in this
> detail, a new GUC option, "debug_print_raw_parse", has been added.
>
> When starting the PostgreSQL process with "-d N", and N is 3 or higher,
> debug_print_raw_parse is enabled automatically, alongside
> debug_print_parse.
prion is complaining here:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-09-05%2023%3A03%3A05
I did not look into the details, but this usually points to a
use-after-free problem.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2025-09-06 02:45:42 | Re: pgsql: Allow to log raw parse tree. |
| Previous Message | Tatsuo Ishii | 2025-09-05 22:52:55 | pgsql: Allow to log raw parse tree. |