aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistutil.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2019-06-07 12:43:55 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2019-06-07 12:43:55 +0300
commit12a45a20aa25468c56311e71320bb586c2490836 (patch)
treeb8be4b1d8e3726464d8e7ef605a271fe22509c0a /src/backend/access/gist/gistutil.c
parent17aa054a79961556da8f6bbc158a7786345ac926 (diff)
downloadpostgresql-12a45a20aa25468c56311e71320bb586c2490836.tar.gz
postgresql-12a45a20aa25468c56311e71320bb586c2490836.zip
Fix copy-pasto in freeing memory on error in vacuumlo.
It's harmless to call PQfreemem() with a NULL argument, so the only consequence was that if allocating 'schema' failed, but allocating 'table' or 'field' succeeded, we would leak a bit of memory. That's highly unlikely to happen, so this is just academical, but let's get it right. Per bug #15838 from Timur Birsh. Backpatch back to 9.5, where the PQfreemem() calls were introduced. Discussion: https://www.postgresql.org/message-id/15838-3221652c72c5e69d@postgresql.org
Diffstat (limited to 'src/backend/access/gist/gistutil.c')
0 files changed, 0 insertions, 0 deletions