Re: Indexes on expressions with multiple columns and operators
От | Jehan-Guillaume de Rorthais |
---|---|
Тема | Re: Indexes on expressions with multiple columns and operators |
Дата | |
Msg-id | 20250919163745.1dfc1044@karst обсуждение исходный текст |
Ответ на | Re: Indexes on expressions with multiple columns and operators (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-performance |
On Thu, 18 Sep 2025 12:59:11 -0400 Tom Lane <tgl@sss.pgh.pa.us> wrote: > Jehan-Guillaume de Rorthais <jgdr@dalibo.com> writes: > > On a fresh instance from HEAD with its default configuration, it shows: > > > Index Scan using foo_s_idx on foo (cost=0.29..8.39 rows=33333 width=13) > > Index Cond: (s(crit, ackid) = true) > > > It seems statistics shown in "pg_stats" view for function "s()" are good. > > The query itself even have the same costs than the query using the syntax > > tips you provide before. > > > However, the estimated row number seems wrong in regard with the costs shown > > and statistics. > > Yeah. The problem is that clause_selectivity_ext fails to consider > use of statistics if the clause looks like "bool_valued_function(...)". > If it looks like "bool_valued_function(...) = true", that goes down > a different code path that does the right thing. Oh, OK, I understand. Thanks for your explanations! Regards,
В списке pgsql-performance по дате отправления: