aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2019-08-13 10:55:58 +0900
committerMichael Paquier <michael@paquier.xyz>2019-08-13 10:55:58 +0900
commit4c0b9cf9e073ca2dc95a75fe983d90fd518864fb (patch)
treea8c9eff33f3cd92e9015f2d71893e6dbc882049e /src/backend/access/gist
parenta05fa2c0e77535470b6ee1029671eb41c612f4ef (diff)
downloadpostgresql-4c0b9cf9e073ca2dc95a75fe983d90fd518864fb.tar.gz
postgresql-4c0b9cf9e073ca2dc95a75fe983d90fd518864fb.zip
Fix random regression failure in test case "temp"
This test case could fail because of an incorrect result ordering when looking up at pg_class entries. This commit adds an ORDER BY to the culprit query. The cause of the failure was likely caused by a plan switch. By default, the planner would likely choose an index-only scan or an index scan, but even a small change in the startup cost could have caused a bitmap heap scan to be chosen, causing the failure. While on it, switch some filtering quals to a regular expression as per an idea of Tom Lane. As previously shaped, the quals would have selected any relations whose name begins with "temp". And that could cause failures if another test running in parallel began to use similar relation names. Per report from buildfarm member anole, though the failure was very rare. This test has been introduced by 319a810, so backpatch down to v10. Discussion: https://postgr.es/m/20190807132422.GC15695@paquier.xyz Backpatch-through: 10
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions