| From: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
|---|---|
| To: | Frédéric Yhuel <frederic(dot)yhuel(at)dalibo(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>, Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>, Christophe Courtois <christophe(dot)courtois(at)dalibo(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Subject: | Re: Indexes on expressions with multiple columns and operators |
| Date: | 2025-10-13 13:56:59 |
| Message-ID: | 57d14051-d5c6-4af2-a6e9-7e362dea354d@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 23/9/2025 15:31, Frédéric Yhuel wrote:
> To get back to the topic of partitioned statistics, do you know if SQL
> Server is smart enough to handle this case [1] that we discussed last
> year? (with filtered statistics)
>
> [1] https://www.postgresql.org/message-id/flat/b860c71a-7cab-4d88-
> ad87-8c1f2eea9ae8%40dalibo.com
Not sure. After changing employers recently, I've lost access to the SQL
Server instance :( and can't check how smart it is. However, as I
recall, they design many features, and sometimes their optimiser finds a
good solution/estimation through an unexpected approach.
--
regards, Andrei Lepikhov,
pgEdge
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2025-10-13 14:00:35 | Re: Indexes on expressions with multiple columns and operators |
| Previous Message | Pavel Stehule | 2025-10-12 04:57:56 | Re: proposal: schema variables |