]> granicus.if.org Git - postgresql/commit
Use fuzzy path cost tiebreaking rule in our oldest supported branches.
authorTom Lane <tgl@sss.pgh.pa.us>
Sat, 15 Aug 2015 15:02:17 +0000 (11:02 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Sat, 15 Aug 2015 15:02:34 +0000 (11:02 -0400)
commit9d6af7367e7b079c021c285f03128bad531b667e
tree93db6c8eebd5ec46fec68867bd3ea4ddd2e79cb2
parent24906bbc22650b5bfefd1594de557dc83a71cee5
Use fuzzy path cost tiebreaking rule in our oldest supported branches.

We've been doing it that way since 9.2, cf commit 33e99153e93b9acc,
but some recently-added regression test cases are making a few buildfarm
members fail (ie choose the "wrong" plan) in 9.0 and 9.1 due to
platform-specific roundoff differences in cost calculations.  To fix,
back-port the patch that made add_path treat cost difference ratios of
less than 1e-10 as equal.
src/backend/optimizer/util/pathnode.c