Re: Raw parse tree is not dumped to log

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Raw parse tree is not dumped to log
Date: 2025-08-01 08:10:16
Message-ID: CAEoWx2mf_X70-ZXMWiWernCkLk7cey_Qjq2-V7AxQ1gYyM-jJA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Tatsuo, thanks for pointing out the past conversation.

So, the requirement got 1 more vote from me. But to not make noise to
people who are not interested in raw parse tree, I guess it's better to add
a new option "debug_print_raw_parse". For people who are interested in raw
parse tree, turning on a flag once is much more convenient than typing a
command in the debugger for every trace.

I will wait to see if Tom still objects to adding that. I will not make the
code change unless I see a hint of "go".

Chao Li (Evan)
------------------------------
HighGo Software Inc.
https://www.highgo.com/

Tatsuo Ishii <ishii(at)postgresql(dot)org> 于2025年8月1日周五 15:18写道:

> > Before submitting this trivial patch, I still want to confirm with the
> > community if it's intentional to not dump raw parse tree?
>
> For your reference, here's the past discussion:
>
> https://www.postgresql.org/message-id/flat/20080730.172949.132921436.t-ishii%40sraoss.co.jp
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS K.K.
> English: http://www.sraoss.co.jp/index_en/
> Japanese:http://www.sraoss.co.jp
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2025-08-01 08:13:46 Re: When creating index, why pointing to old version of tuple
Previous Message Zhijie Hou (Fujitsu) 2025-08-01 08:03:10 RE: Add support for specifying tables in pg_createsubscriber.