Re: Using Expanded Objects other than Arrays from plpgsql

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Pavel Borisov <pashkin.elfe@gmail.com>

Cc: Andrey Borodin <x4mmm@yandex-team.ru>, Michel Pelletier <pelletier.michel@gmail.com>, Pavel Stehule <pavel.stehule@gmail.com>, pgsql-hackers@lists.postgresql.org

Date: 2025-01-31T01:53:41Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Allow extension functions to participate in in-place updates.
- c366d2bdba7c 18.0 landed
Implement new optimization rule for updates of expanded variables.
- 6c7251db0ce1 18.0 landed
Detect whether plpgsql assignment targets are "local" variables.
- 36fb9ef269a0 18.0 landed
Preliminary refactoring of plpgsql expression construction.
- a654af21ae52 18.0 landed
Refactor pl_funcs.c to provide a usage-independent tree walker.
- 6a7283dd2f1c 18.0 landed
Generalize plpgsql's heuristic for importing expanded objects.
- 534d0ea6c2b9 18.0 landed

Attachments

v4-0001-Preliminary-refactoring.patch (text/x-diff) patch v4-0001
v4-0002-Detect-whether-plpgsql-assignment-targets-are-loc.patch (text/x-diff) patch v4-0002
v4-0003-Implement-new-optimization-rule-for-updates-of-ex.patch (text/x-diff) patch v4-0003
v4-0004-Allow-extension-functions-to-participate-in-in-pl.patch (text/x-diff) patch v4-0004

Pavel Borisov <pashkin.elfe@gmail.com> writes:
> I started looking at the patchset.
> Recently it got conflicts with changes to yyparse (473a575e05979b4db).
> Could you rebase it and also do naming changes proposed by Andrew
> Borodin, which I definitely agree with?

Hmm, it seemed to still apply for me.  But anyway, I needed to make
the other changes, so here's v4.

			regards, tom lane