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: Michel Pelletier <pelletier.michel@gmail.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>,
pgsql-hackers@lists.postgresql.org
Date: 2025-01-15T18:09:03Z
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
- v3-0001-Preliminary-refactoring.patch (text/x-diff) patch v3-0001
- v3-0002-Detect-whether-plpgsql-assignment-targets-are-loc.patch (text/x-diff) patch v3-0002
- v3-0003-Implement-new-optimization-rule-for-updates-of-ex.patch (text/x-diff) patch v3-0003
- v3-0004-Allow-extension-functions-to-participate-in-in-pl.patch (text/x-diff) patch v3-0004
I noticed that v2 of this patch series failed to apply after 7b27f5fd3, so here's v3. No non-trivial changes. regards, tom lane