diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2011-09-16 04:27:49 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2011-09-16 04:27:49 -0400 |
| commit | 0a6cc28500b7a8db7a27cbd0d75e18837fb2e367 (patch) | |
| tree | 128d6c3e8afa7b5eac4fa66a115f4c9a61b28ef9 /src/backend/access/gist/gist.c | |
| parent | e6faf910d75027bdce7cd0f2033db4e912592bcc (diff) | |
| download | postgresql-0a6cc28500b7a8db7a27cbd0d75e18837fb2e367.tar.gz postgresql-0a6cc28500b7a8db7a27cbd0d75e18837fb2e367.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/gist.c')
0 files changed, 0 insertions, 0 deletions