Fix freeing old values in index_store_float8_orderby_distances()
authorAlexander Korotkov <[email protected]>
Thu, 19 Sep 2019 22:10:56 +0000 (01:10 +0300)
committerAlexander Korotkov <[email protected]>
Thu, 19 Sep 2019 22:19:08 +0000 (01:19 +0300)
commit8c8a267201bebb0edeaab2a76b7d3bcc9739924f
tree2d8b34940beeeee24fb2e5825ee593575e8dc069
parent6cae9d2c10e151f741e7bc64a8b70bb2615c367c
Fix freeing old values in index_store_float8_orderby_distances()

6cae9d2c10 has added an error in freeing old values in
index_store_float8_orderby_distances() function.  It looks for old value in
scan->xs_orderbynulls[i] after setting a new value there.
This commit fixes that.  Also it removes short-circuit in handling
distances == NULL situation.  Now distances == NULL will be treated the same
way as array with all null distances.  That is, previous values will be freed
if any.

Reported-by: Tom Lane, Nikita Glukhov
Discussion: https://postgr.es/m/CAPpHfdu2wcoAVAm3Ek66rP%3Duo_C-D84%2B%2Buf1VEcbyi_caBXWCA%40mail.gmail.com
Discussion: https://postgr.es/m/426580d3-a668-b9d1-7b8e-f74d1a6524e0%40postgrespro.ru
Backpatch-through: 12
src/backend/access/index/indexam.c