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

From Laurenz Albe
Subject Re: subquery plan rows = 1, but it's merge joined instead of index lookup
Date
Msg-id 1a9f049f436b01ef2ad3ed0e283c50e54be8f4e9.camel@cybertec.at
Whole thread Raw
In response to [MASSMAIL] subquery plan rows = 1, but it's merge joined instead of index lookup  (ilya Basin <basinilya@gmail.com>)
Responses Re: subquery plan rows = 1, but it's merge joined instead of index lookup  (Ilya Basin <basinilya@gmail.com>)
List pgsql-general
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: Tom Lane
Date:
Subject: Re: (When) can a single SQL statement return multiple result sets?
Next
From: veem v
Date:
Subject: [MASSMAIL]Question on trigger