Re: Using Expanded Objects other than Arrays from plpgsql - Mailing list pgsql-hackers

From Michel Pelletier
Subject Re: Using Expanded Objects other than Arrays from plpgsql
Date
Msg-id CACxu=vJ250gdGF0HPzBEjCX+dDWVvum3P4Vuxg+B_VJ7x69h8A@mail.gmail.com
Whole thread Raw
In response to Re: Using Expanded Objects other than Arrays from plpgsql  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Using Expanded Objects other than Arrays from plpgsql
List pgsql-hackers
On Sun, Feb 2, 2025 at 1:57 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
I wrote:
> Hmm, it seemed to still apply for me.  But anyway, I needed to make
> the other changes, so here's v4.

PFA v5.  The new 0001 patch refactors the free_xxx infrastructure
to create plpgsql_statement_tree_walker(), and then in what's now
0003 we can use that instead of writing a lot of duplicate code.

Thanks Tom!  These patches apply for me and all my tests and benchmarks are still good.

-Michel

pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: pgbench with partitioned tables
Next
From: Amit Kapila
Date:
Subject: Re: Increased work_mem for "logical replication tablesync worker" only?