| From: | Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com> |
|---|---|
| To: | Donghang Lin <donghanglin(at)gmail(dot)com> |
| Cc: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: bt_index_parent_check and concurrently build indexes |
| Date: | 2025-06-03 20:26:09 |
| Message-ID: | CADzfLwVKqeq4qQJM9zimuMY9j7x4cyBtcKGb+P9FcAmpwke6oA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello, Donghang!
> One suggestion to this change is that we might need to update the amcheck doc to reflect that
> "This consists of a “dummy” CREATE INDEX CONCURRENTLY operation" rather than "CREATE INDEX" operation.
+1, done. Also fixed some typos in the commit message.
Best regards,
Mikhail.
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-amcheck-Fix-bt_index_parent_check-behavior-with-C.patch | application/octet-stream | 9.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2025-06-03 20:46:31 | Re: C11 / VS 2019 |
| Previous Message | Nathan Bossart | 2025-06-03 20:23:42 | Re: like pg_shmem_allocations, but fine-grained for DSM registry ? |