Re: bt_index_parent_check and concurrently build indexes

Поиск
Список
Период
Сортировка
От Andrey M. Borodin
Тема Re: bt_index_parent_check and concurrently build indexes
Дата
Msg-id DAED842D-7AF8-447D-9411-5F1DBF9252B0@yandex-team.ru
обсуждение исходный текст
Ответ на Re: bt_index_parent_check and concurrently build indexes  ("Andrey M. Borodin" <x4mmm@yandex-team.ru>)
Список pgsql-hackers

> On 13 Dec 2024, at 04:59, Michail Nikolaev <michail.nikolaev@gmail.com> wrote:
> <v3-0001-amcheck-Fix-bt_index_parent_check-behavior-with-C.patch>

+# Copyright (c) 2021-2024, PostgreSQL Global Development Group

I think usually write only commit year. Something tells me you can safely write 2025 there.

+Test::More->builder->todo_start('filesystem bug')
+  if PostgreSQL::Test::Utils::has_wal_read_bug;

Can't wrap my head why do you need this?

+# it fails, because it is expect to find the deleted row in index

I think this comment describes behavior before the fix in present tense.

-        if (snapshot != SnapshotAny)
-            UnregisterSnapshot(snapshot);

Snapshot business seems incorrect to me here...


Best regards, Andrey Borodin.


В списке pgsql-hackers по дате отправления: