diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2009-01-07 20:39:05 +0000 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2009-01-07 20:39:05 +0000 |
commit | 323dd9f3203c49ebcea35a5b2f436e88e1a2039e (patch) | |
tree | c21e87b0beb6ee520f06b29aff47724113da2f02 /src/backend/access/gist/gist.c | |
parent | 72a3bc4a1d578df0c51534c8bf7dc918ac6c8595 (diff) | |
download | postgresql-323dd9f3203c49ebcea35a5b2f436e88e1a2039e.tar.gz postgresql-323dd9f3203c49ebcea35a5b2f436e88e1a2039e.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/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions