Home > mailing lists

Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not? - Mailing list pgsql-hackers

From	Andy Fan
Subject	Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not?
Date	May 17, 2021 05:52:22
Msg-id	CAKU4AWr362Hz1MEGeN_hsqjgwQRX7KUyPXQw_tPT-KETToGMKA@mail.gmail.com Whole thread Raw
In response to	Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not? (Tom Lane <tgl@sss.pgh.pa.us>)
Responses	Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not?
List	pgsql-hackers

So now you have to figure out
what the selectivity of that is after the application of the partially
redundant IN clauses.

Would marking the new added RestrictInfo.norm_selec > 1 be OK?

clause_selectivity_ext

/*
* If the clause is marked redundant, always return 1.0.
*/
if (rinfo->norm_selec > 1)
return (Selectivity) 1.0;

Best Regards

From: Bruce Momjian
Date: 17 May 2021, 05:51:02
Subject: Re: PG 14 release notes, first draft

From: Bruce Momjian
Date: 17 May 2021, 06:06:28
Subject: Re: PG 14 release notes, first draft