Re: Is it possible to specify minimum number of rows planner should consider?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Timothy Garnett <tgarnett(at)panjiva(dot)com>
Cc: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: Is it possible to specify minimum number of rows planner should consider?
Date: 2020-09-28 21:06:51
Message-ID: 408272.1601327211@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Timothy Garnett <tgarnett(at)panjiva(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Matthew Bellew 2020-09-28 21:45:38 Re: Is it possible to specify minimum number of rows planner should consider?
Previous Message Timothy Garnett 2020-09-28 20:12:37 Is it possible to specify minimum number of rows planner should consider?