Re: bt_index_parent_check and concurrently build indexes

From: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>, Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Donghang Lin <donghanglin(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andrey Borodin <amborodin86(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
Subject: Re: bt_index_parent_check and concurrently build indexes
Date: 2025-09-23 11:13:18
Message-ID: CADzfLwVr2hYZn0BuO4B_T1JGzEfshYOqJeycLFDpMVT=F78ioA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello, everyone!

Could someone please take a look?

We have a confirmed bug, which happens in production [0], probably
needs to be backported and has a simple patch to address for about 9
months already....
I am not trying to blame someone, just to highlight how it sometimes
feels from the non-committer side.

Best regards,
Mikhail.

[0]: https://www.postgresql.org/message-id/flat/CAA%3DD8a2Q23miHJtHRDk_TSQKvd6oHk8wGpkQt99B%3D9yd-oqnfg%40mail.gmail.com#e563629249821b5f61e44a635b758ad1

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2025-09-23 11:58:56 Re: Inconsistent Behavior of GROUP BY ROLLUP in v17 vs master
Previous Message Michael Paquier 2025-09-23 11:07:13 Re: [PATCH] Add tests for Bitmapset