> On 13 Jul 2026, at 20:17, Tomas Vondra <tomas@vondra.me> wrote:
> On 7/13/26 13:15, wenhui qiu wrote:
>> The patch also optimizes the legacy path with a rolling hash, indexed
>> history rings, bounded candidate searches, word/SIMD match extension,
>> and an AVX2 implementation selected by PostgreSQL's runtime CPU check.
>> Other platforms use PostgreSQL's existing SIMD abstraction.
>>
>
> This, on the other hand would be a *huge* improvement for all existing
> systems with a lot of data compressed with pglz (and there's fair amount
> of those). If we could just make them faster by optimizing the code,
> that seems very desirable.
+1, if optimizing the code can unlock performance improvements while being
backwards compatible it would be a very big win.
--
Daniel Gustafsson
