diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2009-01-07 20:39:15 +0000 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2009-01-07 20:39:15 +0000 |
commit | c23bd9232fb1d757ec8d422422232d789556860a (patch) | |
tree | 7fb1cf419c1e618a0da97961579060a4408c57c7 /src/tutorial/advanced.source | |
parent | 7673ed269addea2ea5a065f64cd3e6afc0344eac (diff) | |
download | postgresql-c23bd9232fb1d757ec8d422422232d789556860a.tar.gz postgresql-c23bd9232fb1d757ec8d422422232d789556860a.zip |
Insert conditional SPI_push/SPI_pop calls into InputFunctionCall,
OutputFunctionCall, and friends. This allows SPI-using functions to invoke
datatype I/O without concern for the possibility that a SPI-using function
will be called (which could be either the I/O function itself, or a function
used in a domain check constraint). It's a tad ugly, but not nearly as ugly
as what'd be needed to make this work via retail insertion of push/pop
operations in all the PLs.
This reverts my patch of 2007-01-30 that inserted some retail SPI_push/pop
calls into plpgsql; that approach only fixed plpgsql, and not any other PLs.
But the other PLs have the issue too, as illustrated by a recent gripe from
Christian Schröder.
Back-patch to 8.2, which is as far back as this solution will work. It's
also as far back as we need to worry about the domain-constraint case, since
earlier versions did not attempt to check domain constraints within datatype
input. I'm not aware of any old I/O functions that use SPI themselves, so
this should be sufficient for a back-patch.
Diffstat (limited to 'src/tutorial/advanced.source')
0 files changed, 0 insertions, 0 deletions