Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Cc: Nate Clark <natec425(at)gmail(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
Date: 2026-11-03 09:32:53
Message-ID: CAHGQGwGkHCLyKHuYNhMBHFk1oZyO2_U_m+soqT38aT_2qFjQ4A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Oct 5, 2026 at 12:37 PM Ayush Tiwari
<ayushtiwari(dot)slg01(at)gmail(dot)com> wrote:
> Thanks for the report and patch. The fix looks right to me.

This should be backpatched to all supported versions?

The fix doesn't repair existing indexes. Right? If so, we should advise users
to REINDEX all existing gist_trgm_ops indexes after upgrading to a minor
release containing the fix?

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Ayush Tiwari 2026-11-03 10:35:55 Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
Previous Message Rahul 2026-11-03 08:39:54 Re: Wrong results: hashed SubPlan referenced twice after OR-qual extraction reuses a stale hash table (13 to 19beta4)