Tom Lane 745e6edaae Fix SPI_cursor_open() and SPI_is_cursor_plan() to push the SPI stack before ... doing anything interesting, such as calling RevalidateCachedPlan(). The necessity of this is demonstrated by an example from Willem Buitendyk: during a replan, the planner might try to evaluate SPI-using functions, and so we'd better be in a clean SPI context. A small downside of this fix is that these two functions will now fail outright if called when not inside a SPI-using procedure (ie, a SPI_connect/SPI_finish pair). The documentation never promised or suggested that that would work, though; and they are normally used in concert with other functions, mainly SPI_prepare, that always have failed in such a case. So the odds of breaking something seem pretty low. In passing, make SPI_is_cursor_plan's error handling convention clearer, and fix documentation's erroneous claim that SPI_cursor_open would return NULL on error. Before 8.3 these functions could not invoke replanning, so there is probably no need for back-patching.		2008-02-12 04:09:44 +00:00
..
FAQ	Update FAQ for most recent release as 8.3.	2008-02-01 02:55:41 +00:00
sgml	Fix SPI_cursor_open() and SPI_is_cursor_plan() to push the SPI stack before	2008-02-12 04:09:44 +00:00
Makefile	Don't ship spi_* man pages. (We don't do that anyway, but now it's automatic.)	2006-12-02 01:25:50 +00:00