Re: subquery plan rows = 1, but it's merge joined instead of index lookup - Mailing list pgsql-general

From Ilya Basin
Subject Re: subquery plan rows = 1, but it's merge joined instead of index lookup
Date
Msg-id 1e2744d1-49f2-4c76-bc10-d064f81a3982@gmail.com
Whole thread Raw
In response to Re: subquery plan rows = 1, but it's merge joined instead of index lookup  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-general
Yes! "set join_collapse_limit = 9" was enough to fix the plan, thanks Laurenz.
I will set both to 11.


-------- Original Message --------
From: Laurenz Albe [mailto:laurenz.albe@cybertec.at]
Sent: Thursday, April 11, 2024 at 14:21 UTC
To: ilya Basin; pgsql-general@lists.postgresql.org
Subject: subquery plan rows = 1, but it's merge joined instead of index lookup

On Thu, 2024-04-11 at 15:57 +0300, ilya Basin wrote:
Is there some complexity limit after which the planner starts acting dumb?

Yes, "join_collapse_limit" and "from_collapse_limit".
You can try increasing them.

Yours,
Laurenz Albe




pgsql-general by date:

Previous
From: veem v
Date:
Subject: [MASSMAIL]Question on trigger
Next
From: Adrian Klaver
Date:
Subject: Re: Question on trigger