]> 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:33 +0000 (11:02 -0400)
commit3218f8c33612baca0a1f44d4a243c598ddebad9d
treeaf3dd0d11d49545d01c598b53bbb5e6da08caae6
parent8749aafde2179de243bc8ffeec23a28a94ec5def
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