aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/trigger.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2002-10-14 04:20:52 +0000
committerBruce Momjian <bruce@momjian.us>2002-10-14 04:20:52 +0000
commit1f653ec31ef0f88af1216c0631605e859b4794a5 (patch)
treea2177dd7b6ef7f35f29115ae9d3730b7ba5ca432 /src/backend/commands/trigger.c
parentdaaf999fcbfaab378e4ac2800d26cc04f12f1500 (diff)
downloadpostgresql-1f653ec31ef0f88af1216c0631605e859b4794a5.tar.gz
postgresql-1f653ec31ef0f88af1216c0631605e859b4794a5.zip
I have attached two patches as per:
1) pltcl: Add SPI_freetuptable() calls to avoid memory leaks (Me + Neil Conway) Change sprintf()s to snprintf()s (Neil Conway) Remove header files included elsewhere (Neil Conway) 2)plpython: Add SPI_freetuptable() calls to avoid memory leaks Cosemtic change to remove a compiler warning Notes: I have tested pltcl.c for a) the original leak problem reported for the repeated call of spi_exec in a TCL fragment and b) the subsequent report resulting from the use of spi_exec -array in a TCL fragment. The plpython.c patch is exactly the same as that applied to make revision 1.23, the plpython_schema.sql and feature.expected sections of the patch are also the same as last submited, applied and subsequently reversed out. It remains untested by me (other than via make check). However, this should be safe provided PyString_FromString() _copies_ the given string to make a PyObject. Nigel J. Andrews
Diffstat (limited to 'src/backend/commands/trigger.c')
0 files changed, 0 insertions, 0 deletions