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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: shihao zhong <zhong950419(at)gmail(dot)com>
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 22:25:17
Message-ID: avD2zTs4J4WU-83o@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Nov 07, 2026 at 07:02:15PM -0500, shihao zhong wrote:
> v2 uses repeat() and sets the column to STORAGE
> EXTERNAL so it stays uncompressed, like toast.sql does.

This version works here, and the test is much, much cheaper than in
your v1 where most of the extra time was spent to build the long
value. Thanks for updating the patch.

(We're in freeze period for the release, so I'll get back to it in 48
hours or so after the version tags are pushed.)
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2026-11-08 23:07:45 Re: BUG #19853: Memoize returns wrong rows when the join operator is hashable but its equality semantics differ from
Previous Message Ruohang Feng 2026-11-08 15:12:12 Re: BUG #19788: Chinese translation uses incorrect term for “transaction” in “no transaction is in progress”