Re: [PATCH] ANALYZE: hash-accelerate MCV tracking for equality-only types
John Naylor <johncnaylorls@gmail.com>
From: John Naylor <johncnaylorls@gmail.com>
To: Chengpeng Yan <chengpeng_yan@outlook.com>
Cc: Tatsuya Kawata <kawatatatsuya0913@gmail.com>, Ilia Evdokimov <ilya.evdokimov@tantorlabs.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2026-02-03T05:39:48Z
Lists: pgsql-hackers
On Tue, Feb 3, 2026 at 11:33 AM Chengpeng Yan <chengpeng_yan@outlook.com> wrote: > That said, if other community members would prefer the simpler one-step > update for readability, I’m happy to switch. To evaluate that, it would be easier if the patch were split into two commits, one with the simple step approach, and one that changes to the other approach. Also, we have some places that switch from e.g. an array to a hash table once a collection gets above a certain threshold. In this case, however, having less than 100 stat target is unheard of, in my experience. It's only a tiny amount of code, but it doesn't seem worth special-casing. Others may have a different opinion, and I'm not sure we don't already have this behavior elsewhere. -- John Naylor Amazon Web Services
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Speed up eqjoinsel() with lots of MCV entries.
- 057012b205a0 19 (unreleased) cited