diff options
| author | David Rowley <drowley@postgresql.org> | 2021-07-13 13:31:29 +1200 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2021-07-13 13:31:29 +1200 |
| commit | d7f10f39ca2d84220a96dba473371c6de0cc41d7 (patch) | |
| tree | b119ecf6c77bf946fe27bb4fb5958c20e3c3a12d /src/backend | |
| parent | b55e478a4c2ca506cacf33691db305a50dc43cc2 (diff) | |
Robustify tuplesort's free_sort_tuple function
41469253e went to the trouble of removing a theoretical bug from
free_sort_tuple by checking if the tuple was NULL before freeing it. Let's
make this a little more robust by also setting the tuple to NULL so that
should we be called again we won't end up doing a pfree on the already
pfree'd tuple. Per advice from Tom Lane.
Discussion: https://postgr.es/m/3188192.1626136953@sss.pgh.pa.us
Backpatch-through: 9.6, same as 41469253e
Diffstat (limited to 'src/backend')
| -rw-r--r-- | src/backend/utils/sort/tuplesort.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/backend/utils/sort/tuplesort.c b/src/backend/utils/sort/tuplesort.c index 513b2d933f8..80bc67bc9e5 100644 --- a/src/backend/utils/sort/tuplesort.c +++ b/src/backend/utils/sort/tuplesort.c @@ -4462,5 +4462,6 @@ free_sort_tuple(Tuplesortstate *state, SortTuple *stup) { FREEMEM(state, GetMemoryChunkSpace(stup->tuple)); pfree(stup->tuple); + stup->tuple = NULL; } } |