postgres

History

Tom Lane c0486e9dea Fix plpgsql's handling of "simple" expression evaluation. In general, expression execution state trees aren't re-entrantly usable, since functions can store private state information in them. For efficiency reasons, plpgsql tries to cache and reuse state trees for "simple" expressions. It can get away with that most of the time, but it can fail if the state tree is dirty from a previous failed execution (as in an example from Alvaro) or is being used recursively (as noted by me). Fix by tracking whether a state tree is in use, and falling back to the "non-simple" code path if so. This results in a pretty considerable speed hit when the non-simple path is taken, but the available alternatives seem even more unpleasant because they add overhead in the simple path. Per idea from Heikki. Back-patch to all supported branches.		15 years ago
..
backend	Before removing backup_label and irrevocably changing pg_control file, check	15 years ago
bin	Translation updates for 8.1.22	15 years ago
include	Tag 8.1.22	15 years ago
interfaces	Tag 8.1.22	15 years ago
makefiles	Add $(CFLAGS) to the simplified build rule for .so libraries on Darwin.	19 years ago
pl	Fix plpgsql's handling of "simple" expression evaluation.	15 years ago
port	Tag 8.1.22	15 years ago
template	…
test	Fix plpgsql's handling of "simple" expression evaluation.	15 years ago
timezone	Convert cvsignore to gitignore, and add .gitignore for build targets.	15 years ago
tools	Create a script to handle stamping release version numbers into files,	18 years ago
tutorial	Use SQL standard '' rather than \' for tutorial/sample code.	20 years ago
utils	…
.gitignore	Convert cvsignore to gitignore, and add .gitignore for build targets.	15 years ago
DEVELOPERS	…
Makefile	…
Makefile.global.in	…
Makefile.shlib	Fix out-of-order inclusion of -L switches from LDFLAGS on AIX and HPUX.	20 years ago
bcc32.mak	…
nls-global.mk	…
win32.mak	…