diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2008-03-07 15:59:09 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2008-03-07 15:59:09 +0000 |
| commit | bdffbddd061ef3720c735a17b9dd3d4fad918928 (patch) | |
| tree | 3ed5bdd8c0a4ea8ea69baf64e690b649a3842fee /src/backend/access/gist/gistutil.c | |
| parent | b7a2ab5b6ea0eee67f5e0fa6ea6a8faef4ddac6f (diff) | |
| download | postgresql-bdffbddd061ef3720c735a17b9dd3d4fad918928.tar.gz postgresql-bdffbddd061ef3720c735a17b9dd3d4fad918928.zip | |
Change hashscan.c to keep its list of active hash index scans in
TopMemoryContext, rather than scattered through executor per-query contexts.
This poses no danger of memory leak since the ResourceOwner mechanism
guarantees release of no-longer-needed items. It is needed because the
per-query context might already be released by the time we try to clean up
the hash scan list. Report by ykhuang, diagnosis by Heikki.
Back-patch to 8.0, where the ResourceOwner-based cleanup was introduced.
The given test case does not fail before 8.2, probably because we rearranged
transaction abort processing somehow; but this coding is undoubtedly risky
so I'll patch 8.0 and 8.1 anyway.
Diffstat (limited to 'src/backend/access/gist/gistutil.c')
0 files changed, 0 insertions, 0 deletions