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

From: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
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-04 15:48:57
Message-ID: CAJTYsWXsSUrxpL7tF_AcDX-c5BYLvOes7_W==f1Y_pMgUSgQNQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On Wed, 4 Nov 2026 at 11:13, shihao zhong <zhong950419(at)gmail(dot)com> wrote:
>
> Thanks for the report. With only two entries, the cache of the second
> one is used before it is filled.

+1

> Your two column case is harmless. With one column, the index can miss
> rows until REINDEX.
>
> The attached patch fills the cache earlier and adds a test.

Thanks for the patch, it looks good to me.

Regards,
Ayush

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Ayush Tiwari 2026-11-04 15:58:47 Re: BUG #19603: Vuln47: distance_taxicab and distance_chebyshev silently return 0 instead of NaN when a cube coordin
Previous Message Daniel Gustafsson 2026-11-04 15:27:17 Re: set_config(‘search_path’) does not truncate names over 63 bytes, unlike SET