pgsql: Add SPI_push/SPI_pop calls so that datatype input and output - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Add SPI_push/SPI_pop calls so that datatype input and output
Date
Msg-id 20070130180240.EAC879FB411@postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Add SPI_push/SPI_pop calls so that datatype input and output functions called
by plpgsql can themselves use SPI --- possibly indirectly, as in the case
of domain_in() invoking plpgsql functions in a domain check constraint.
Per bug #2945 from Sergiy Vyshnevetskiy.

Somewhat arbitrarily, I've chosen to back-patch this as far as 8.0.  Given
the lack of prior complaints, it doesn't seem critical for 7.x.

Tags:
----
REL8_0_STABLE

Modified Files:
--------------
    pgsql/src/pl/plpgsql/src:
        pl_exec.c (r1.127.4.5 -> r1.127.4.6)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/pl_exec.c.diff?r1=1.127.4.5&r2=1.127.4.6)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Add SPI_push/SPI_pop calls so that datatype input and output
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Repair oversights in the mechanism used to store compiled plpgsql