Re: bt_index_parent_check and concurrently build indexes

Donghang Lin <donghanglin@gmail.com>

From: Donghang Lin <donghanglin@gmail.com>

To: Álvaro Herrera <alvherre@kurilemu.de>

Cc: Mihail Nikalayeu <mihailnikalayeu@gmail.com>, Peter Geoghegan <pg@bowt.ie>, Michael Paquier <michael@paquier.xyz>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Andrey Borodin <amborodin86@gmail.com>, Matthias van de Meent <boekewurm+postgres@gmail.com>

Date: 2025-12-21T16:18:28Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

amcheck: Fix snapshot usage in bt_index_parent_check
- e1a327dc4dcb 17.8 landed
- dcddd6987197 15.16 landed
- 607a67c5e657 14.21 landed
- 3c83a2a0ace9 18.2 landed
- 1f28982e4094 19 (unreleased) landed
- 098a1fab8a9b 16.12 landed
- df93f94dda51 18.2 landed
- ce2f575b7cf4 17.8 landed
- 6bd469d26aca 19 (unreleased) landed
Teach contrib/amcheck to check the unique constraint violation
- 5ae2087202af 17.0 cited

Attachments

0001-Fix-the-comment-for-snapshot-field-BtreeCheckState.patch (application/octet-stream) patch 0001

Hi Álvaro,


> > I think we'll have another chance to reflect that the issue is since
> > 7f563c09f890 but not 5ae2087202af in master for this fix. I can give
> > it a try.
>
> Go ahead.
>

Attach the fix for the inaccurate comment in master.

Thanks,
Donghang