Re: Why enable_hashjoin Completely disables HashJoin - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Why enable_hashjoin Completely disables HashJoin
Date
Msg-id CA+TgmobFF9HwC_vVzTsrrC5nUs4U5ugE7w3=UXgKfNbAJAqaRg@mail.gmail.com
Whole thread Raw
In response to Re: Why enable_hashjoin Completely disables HashJoin  (Quan Zongliang <quanzongliang@yeah.net>)
List pgsql-hackers
On Tue, Apr 4, 2023 at 3:38 AM Quan Zongliang <quanzongliang@yeah.net> wrote:
> Because someone noticed that when he set enable_hashjoin,
> enable_mergejoin and enable_nestloop to off. The statement seemed to get
> stuck (actually because it chose the NestedLoop path, which took a long
> long time to run).
> If enable_hashjoin and enable_nestloop disable generating these two
> paths. Then enable_nestloop should do the same thing, but it doesn't.

This all seems like expected behavior. If you disable an entire plan
type, you should expect to get some bad plans. And if you disable all
the plan types, you should still expect to get some plan, but maybe an
extremely bad one.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Minimal logical decoding on standbys
Next
From: Tom Lane
Date:
Subject: Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID