diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2011-09-16 04:28:15 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2011-09-16 04:28:15 -0400 |
| commit | ca00f191576183b77ccd60fb29dde86fd96c4b45 (patch) | |
| tree | e4dae1ca047d957f3b5f683bff36d371d4291aa4 /src/backend/access/gist/gistproc.c | |
| parent | 33e111f2258af78f8816dae2eef49c371b94da77 (diff) | |
| download | postgresql-ca00f191576183b77ccd60fb29dde86fd96c4b45.tar.gz postgresql-ca00f191576183b77ccd60fb29dde86fd96c4b45.zip | |
gistendscan() forgot to free so->giststate.
This oversight led to a massive memory leak --- upwards of 10KB per tuple
--- during creation-time verification of an exclusion constraint based on a
GIST index. In most other scenarios it'd just be a leak of 10KB that would
be recovered at end of query, so not too significant; though perhaps the
leak would be noticeable in a situation where a GIST index was being used
in a nestloop inner indexscan. In any case, it's a real leak of long
standing, so patch all supported branches. Per report from Harald Fuchs.
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions