Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit57d3dc2

Browse files
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 parentf695042 commit57d3dc2

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

‎src/backend/access/gist/gistscan.c‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -242,6 +242,7 @@ gistendscan(PG_FUNCTION_ARGS)
242242
GISTScanOpaqueso= (GISTScanOpaque)scan->opaque;
243243

244244
freeGISTstate(so->giststate);
245+
pfree(so->giststate);
245246
MemoryContextDelete(so->queueCxt);
246247
MemoryContextDelete(so->tempCxt);
247248
pfree(so->tmpTreeItem);

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp