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

Поиск

Список

Период

Сортировка

От	Andy Fan
Тема	Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not?
Дата	17 мая 2021 г. 05:52:22
Msg-id	CAKU4AWr362Hz1MEGeN_hsqjgwQRX7KUyPXQw_tPT-KETToGMKA@mail.gmail.com обсуждение исходный текст
Ответ на	Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not? (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы	Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not? (David Rowley <dgrowleyml@gmail.com>)
Список	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

В списке pgsql-hackers по дате отправления:

От: Bruce Momjian
Дата: 17 мая 2021 г., 05:51:02
Сообщение: Re: PG 14 release notes, first draft

От: Bruce Momjian
Дата: 17 мая 2021 г., 06:06:28
Сообщение: Re: PG 14 release notes, first draft