Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries
Date: 2026-11-08 00:02:15
Message-ID: CAGRkXqS9swKbFfPrAyAxHqTiQZTAZMf9whuXDCS8d+-y-xyk0A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> By the way, this test is going to piss buildfarm members that have
> FIPS enabled, where md5() calls fail.

aha. I am not aware of that.

v2 uses repeat() and sets the column to STORAGE
EXTERNAL so it stays uncompressed, like toast.sql does.

Thanks,
Shihao

Attachment Content-Type Size
v2-0001-Fix-gtsvector_picksplit-with-only-two-entries.patch application/octet-stream 3.6 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message shihao zhong 2026-11-07 23:55:04 Re: first_value()/nth_value() with IGNORE NULLS loop forever (EXCLUDE GROUP/TIES, frame past partition end, no ORDER BY)