Re: bt_index_parent_check and concurrently build indexes

From: "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
To: Michail Nikolaev <michail(dot)nikolaev(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bt_index_parent_check and concurrently build indexes
Date: 2024-12-10 12:56:06
Message-ID: 50011793-9DA8-405E-8E17-128DA8B10CA2@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 9 Dec 2024, at 23:51, Michail Nikolaev <michail(dot)nikolaev(at)gmail(dot)com> wrote:
>
> * Modify bt_index_parent_check to use an MVCC snapshot for the heap scan

Hi!

Interesting bug. It's amazing how long it stand, giving that it would be triggered by almost any check after updating a table.

From my POV correct fix direction is to use approach similar to index building.
E.i. remove "if (!state->readonly)" check. Are there any known downsides of this?

Best regards, Andrey Borodin.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey M. Borodin 2024-12-10 13:02:36 Re: Fix bank selection logic in SLRU
Previous Message Yura Sokolov 2024-12-10 12:39:28 Fix bank selection logic in SLRU