Search Postgresql Archives

Re: subquery plan rows = 1, but it's merge joined instead of index lookup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: subquery plan rows = 1, but it's merge joined instead of index lookup
From: Laurenz Albe <laurenz.albe@xxxxxxxxxxx>
Date: Thu, 11 Apr 2024 16:21:38 +0200
In-reply-to: <620cfada-683e-45b7-8513-122b2ffab4d8@gmail.com>
References: <620cfada-683e-45b7-8513-122b2ffab4d8@gmail.com>
User-agent: Evolution 3.50.4 (3.50.4-1.fc39)

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: subquery plan rows = 1, but it's merge joined instead of index lookup
  - From: Ilya Basin

References:
- subquery plan rows = 1, but it's merge joined instead of index lookup
  - From: ilya Basin

Prev by Date: Re: (When) can a single SQL statement return multiple result sets?
Next by Date: Question on trigger
Previous by thread: subquery plan rows = 1, but it's merge joined instead of index lookup
Next by thread: Re: subquery plan rows = 1, but it's merge joined instead of index lookup
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux