aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvacuum.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2009-01-07 20:38:56 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2009-01-07 20:38:56 +0000
commitdeac9488d3715408665cac707c4994e96af8b535 (patch)
tree02359ba7a46c356f308dc0e8911deab379f55c79 /src/backend/access/gist/gistvacuum.c
parent6b88393058ec4c2ceb9b5a99d4c2efeb54e5e69b (diff)
downloadpostgresql-deac9488d3715408665cac707c4994e96af8b535.tar.gz
postgresql-deac9488d3715408665cac707c4994e96af8b535.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/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions