Re: Add OID descriptions to dumped parse/query/plan trees - Mailing list pgsql-hackers

From Chao Li
Subject Re: Add OID descriptions to dumped parse/query/plan trees
Date
Msg-id 21A5DAC2-B62A-4E7A-8619-ABD8D470243D@gmail.com
Whole thread Raw
In response to Re: Add OID descriptions to dumped parse/query/plan trees  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers


On Aug 22, 2025, at 22:10, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Chao Li <li.evan.chao@gmail.com> writes:
When reading dumped parse/query/plan trees, sometime we want to know
what exact type/operator/function an OID stands for. I just added a new
feature that will add some OID descriptions to the dump trees, like:

The extra catalog accesses that could occur might also
cause problems, maybe even deadlocks in some uses.  I'd prefer to
keep the flexibility to be able to call pprint from pretty much
anywhere.

Also, AFAICS this breaks re-reading of dump trees, which breaks all
kinds of stuff (rules, views, parallel query, etc).

regards, tom lane

Thanks for pointing out that, I withdraw the patch.

--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/




pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: Add support for specifying tables in pg_createsubscriber.
Next
From: Chao Li
Date:
Subject: Fixes a trivial bug in dumped parse/query/plan trees