Re: Is it possible to specify minimum number of rows planner should consider? - Mailing list pgsql-performance

From Tom Lane
Subject Re: Is it possible to specify minimum number of rows planner should consider?
Date
Msg-id 408272.1601327211@sss.pgh.pa.us
Whole thread Raw
In response to Is it possible to specify minimum number of rows planner should consider?  (Timothy Garnett <tgarnett@panjiva.com>)
Responses Re: Is it possible to specify minimum number of rows planner should consider?
List pgsql-performance
Timothy Garnett <tgarnett@panjiva.com> writes:
> Is there some way to tell the planner that unless it's guaranteed by a
> constraint or some such it shouldn't guess that the selectivity of a
> filter/anti-join is 1 row (e.g. minimum to consider is 2 rows unless it's
> guaranteed to be 1 row) or somehow otherwise make it more conservative
> around the worst case possibilities.

There's been some discussion in that area, but it's a hard problem
to solve in general, and especially so if you'd like to not break
a ton of queries that work nicely today.

            regards, tom lane



pgsql-performance by date:

Previous
From: Timothy Garnett
Date:
Subject: Is it possible to specify minimum number of rows planner should consider?
Next
From: Matthew Bellew
Date:
Subject: Re: Is it possible to specify minimum number of rows planner should consider?