Horton
Menu

Re: Indexes on expressions with multiple columns and operators

Frédéric Yhuel <frederic.yhuel@dalibo.com>

View thread
From: Frédéric Yhuel <frederic.yhuel@dalibo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "pgsql-performance@lists.postgresql.org" <pgsql-performance@lists.postgresql.org>, Jehan-Guillaume de Rorthais <jgdr@dalibo.com>, Christophe Courtois <christophe.courtois@dalibo.com>, Laurenz Albe <laurenz.albe@cybertec.at>
Date: 2025-09-19T07:50:26Z
Lists: pgsql-performance 

On 9/18/25 18:40, Tom Lane wrote:
> The attached fixes things so it works like it did pre-a391ff3c3.
> 

Indeed, it works well!

> I spent some time trying to devise a test case, and was reminded
> of why I didn't have one before: it's hard to make a case that
> will be robust enough to not show diffs in the buildfarm.
> I'll keep thinking about that though.

It looks like an interesting homework for an aspiring hacker :-)
So I'll try to devise one, too.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Re-allow using statistics for bool-valued functions in WHERE.

  2. Build out the planner support function infrastructure.

  3. Allow planner to use expression-index stats for function calls in WHERE.