Allow extension functions to participate in in-place updates.
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 11 Feb 2025 17:49:34 +0000 (12:49 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 11 Feb 2025 17:49:34 +0000 (12:49 -0500)
commitc366d2bdba7c3b9b2cca1429d4535866e231ca55
tree114d1f6c13af036eed4c1a2b0198bf796ad82797
parent6c7251db0ce12a83dd03c840e7d0ff7516b27229
Allow extension functions to participate in in-place updates.

Commit 1dc5ebc90 allowed PL/pgSQL to perform in-place updates
of expanded-object variables that are being updated with
assignments like "x := f(x, ...)".  However this was allowed
only for a hard-wired list of functions f(), since we need to
be sure that f() will not modify the variable if it fails.
It was always envisioned that we should make that extensible,
but at the time we didn't have a good way to do so.  Since
then we've invented the idea of "support functions" to allow
attaching specialized optimization knowledge to functions,
and that is a perfect mechanism for doing this.

Hence, adjust PL/pgSQL to use a support function request instead
of hard-wired logic to decide if in-place update is safe.
Preserve the previous optimizations by creating support functions
for the three functions that were previously hard-wired.

Author: Tom Lane <tgl@sss.pgh.pa.us>
Reviewed-by: Andrey Borodin <x4mmm@yandex-team.ru>
Reviewed-by: Pavel Borisov <pashkin.elfe@gmail.com>
Discussion: https://postgr.es/m/CACxu=vJaKFNsYxooSnW1wEgsAO5u_v1XYBacfVJ14wgJV_PYeg@mail.gmail.com
src/backend/utils/adt/array_userfuncs.c
src/backend/utils/adt/arraysubs.c
src/include/catalog/catversion.h
src/include/catalog/pg_proc.dat
src/include/nodes/supportnodes.h
src/pl/plpgsql/src/expected/plpgsql_array.out
src/pl/plpgsql/src/pl_exec.c
src/pl/plpgsql/src/sql/plpgsql_array.sql
src/tools/pgindent/typedefs.list