Re: BUG #19817: CREATE UNIQUE INDEX on a partitioned table can silently attach an invalid, not-ready child index, le

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: dilipbalaut(at)gmail(dot)com
Cc: reshkekirill(at)gmail(dot)com, 303677365(at)qq(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19817: CREATE UNIQUE INDEX on a partitioned table can silently attach an invalid, not-ready child index, le
Date: 2026-11-08 01:15:45
Message-ID: CAGRkXqSZ6nBK=y-NPjKvHS51BOquLUh1w9FoRmp-kOiimApwGQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Dilip,

Thanks for v3. I tested it on current master.

The ON ONLY cases from my last mail work now, and the original
bug is fixed. A duplicate row is caught after a failed CREATE
UNIQUE INDEX CONCURRENTLY, and a good leaf index is built once the
duplicates are gone.

everything is good! +1 from me.

Thanks,
Shihao

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message shihao zhong 2026-11-08 00:02:15 Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries