- Notifications
You must be signed in to change notification settings - Fork5
Commit0a6cc28
committed
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 aGIST index. In most other scenarios it'd just be a leak of 10KB that wouldbe recovered at end of query, so not too significant; though perhaps theleak would be noticeable in a situation where a GIST index was being usedin a nestloop inner indexscan. In any case, it's a real leak of longstanding, so patch all supported branches. Per report from Harald Fuchs.1 parente6faf91 commit0a6cc28
1 file changed
+1
-0
lines changedLines changed: 1 addition & 0 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
240 | 240 |
| |
241 | 241 |
| |
242 | 242 |
| |
| 243 | + | |
243 | 244 |
| |
244 | 245 |
| |
245 | 246 |
| |
|
0 commit comments
Comments
(0)