Re: PGOPTIONS="-fh" make check gets stuck since Postgres 11
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-07-09T02:30:51Z
Lists: pgsql-hackers
On Tue, Jul 9, 2019 at 2:22 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Thomas Munro <thomas.munro@gmail.com> writes: > > Based on a suggestion from Andres (if I recall correctly), I wrapped > > each individual test in savepoint/rollback, and then set just the GUCs > > needed to get the plan shape and execution code path I wanted to > > exercise, and I guess I found that I only needed to disable merge > > joins for some of them. The idea was that the individual tests could > > be understood independently. > > But per this discussion, they can only be "understood independently" > if you make some assumptions about the prevailing values of the > planner GUCs. Yeah. I had obviously never noticed that test script. +1 for just enabling hash joins the top of join_hash.sql in 12+, and the equivalent section in 11's join.sql (which is luckily at the end of the file). -- Thomas Munro https://enterprisedb.com
Commits
-
Force hash joins to be enabled in the hash join regression tests.
- 3955c50f3762 11.5 landed
- cba0fe024e35 13.0 landed
- 5526baf54902 12.0 landed