Protect GIST logic that assumes penalty values can't be negative.

Apparently sane-looking penalty code might return small negative values,
for example because of roundoff error.  This will confuse places like
gistchoose().  Prevent problems by clamping negative penalty values to
zero.  (Just to be really sure, I also made it force NaNs to zero.)
Back-patch to all supported branches.

Alexander Korotkov
This commit is contained in:
Tom Lane 2011-05-31 17:54:06 -04:00
parent 1d6dd87c4b
commit ca76a3956c
2 changed files with 13 additions and 3 deletions

View File

@ -147,6 +147,8 @@
Returns a value indicating the <quote>cost</quote> of inserting the new
entry into a particular branch of the tree. items will be inserted
down the path of least <function>penalty</function> in the tree.
Values returned by <function>penalty</function> should be non-negative.
If a negative value is returned, it will be treated as zero.
</para>
</listitem>
</varlistentry>

View File

@ -13,6 +13,8 @@
*/
#include "postgres.h"
#include <math.h>
#include "access/gist_private.h"
#include "access/heapam.h"
#include "access/reloptions.h"
@ -530,16 +532,22 @@ gistpenalty(GISTSTATE *giststate, int attno,
{
float penalty = 0.0;
if (giststate->penaltyFn[attno].fn_strict == FALSE || (isNullOrig == FALSE && isNullAdd == FALSE))
if (giststate->penaltyFn[attno].fn_strict == FALSE ||
(isNullOrig == FALSE && isNullAdd == FALSE))
{
FunctionCall3(&giststate->penaltyFn[attno],
PointerGetDatum(orig),
PointerGetDatum(add),
PointerGetDatum(&penalty));
/* disallow negative or NaN penalty */
if (isnan(penalty) || penalty < 0.0)
penalty = 0.0;
}
else if (isNullOrig && isNullAdd)
penalty = 0.0;
else
penalty = 1e10; /* try to prevent to mix null and non-null
* value */
penalty = 1e10; /* try to prevent mixing null and non-null
* values */
return penalty;
}