diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2017-12-15 15:24:10 -0500 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2018-01-10 10:20:51 -0500 |
| commit | b3617cdfbba1b5381e9d1c6bc0839500e8eb7273 (patch) | |
| tree | a2c29bd9c2b47c1ebea6e0532b8067d55d3c81b4 /src/backend/executor/spi.c | |
| parent | acc67ffd0a8c728b928958e75b76ee544b64c2d8 (diff) | |
| download | postgresql-b3617cdfbba1b5381e9d1c6bc0839500e8eb7273.tar.gz postgresql-b3617cdfbba1b5381e9d1c6bc0839500e8eb7273.zip | |
Move portal pinning from PL/pgSQL to SPI
PL/pgSQL "pins" internally generated (unnamed) portals so that user code
cannot close them by guessing their names. This logic is also useful in
other languages and really for any code. So move that logic into SPI.
An unnamed portal obtained through SPI_cursor_open() and related
functions is now automatically pinned, and SPI_cursor_close()
automatically unpins a portal that is pinned.
In the core distribution, this affects PL/Perl and PL/Python, preventing
users from manually closing cursors created by spi_query and
plpy.cursor, respectively. (PL/Tcl does not currently offer any cursor
functionality.)
Reviewed-by: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Diffstat (limited to 'src/backend/executor/spi.c')
| -rw-r--r-- | src/backend/executor/spi.c | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/src/backend/executor/spi.c b/src/backend/executor/spi.c index 995f67d2662..96370513e80 100644 --- a/src/backend/executor/spi.c +++ b/src/backend/executor/spi.c @@ -1175,6 +1175,12 @@ SPI_cursor_open_internal(const char *name, SPIPlanPtr plan, { /* Use a random nonconflicting name */ portal = CreateNewPortal(); + + /* + * Make sure the portal doesn't get closed by the user statements we + * execute. + */ + PinPortal(portal); } else { @@ -1413,6 +1419,9 @@ SPI_cursor_close(Portal portal) if (!PortalIsValid(portal)) elog(ERROR, "invalid portal in SPI cursor operation"); + if (portal->portalPinned) + UnpinPortal(portal); + PortalDrop(portal, false); } |