aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistscan.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2005-06-20 22:51:49 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2005-06-20 22:51:49 +0000
commit7d32f099d7ce64d08f458d2e33bce7b28e1293b5 (patch)
tree273e0a290df9a639a997a6c58b6c60a796111dbb /src/backend/access/gist/gistscan.c
parentc541ca6403f02c695bfeb85b6733cbf2c561943c (diff)
downloadpostgresql-7d32f099d7ce64d08f458d2e33bce7b28e1293b5.tar.gz
postgresql-7d32f099d7ce64d08f458d2e33bce7b28e1293b5.zip
exec_eval_datum leaks memory when dealing with ROW or REC values.
It never leaked memory before PG 8.0, so none of the callers are expecting this. Cleanest fix seems to be to make it allocate the needed memory in estate->eval_econtext, where it will be cleaned up by the next exec_eval_cleanup. Per report from Bill Rugolsky.
Diffstat (limited to 'src/backend/access/gist/gistscan.c')
0 files changed, 0 insertions, 0 deletions