| From: | Arseniy Mukhin <arseniy(dot)mukhin(dot)dev(at)gmail(dot)com> |
|---|---|
| To: | solai v <solai(dot)cdac(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: amcheck support for BRIN indexes |
| Date: | 2026-05-20 17:55:53 |
| Message-ID: | CAE7r3MKccGzEHaL5KPDTjZ=7iT3b47NJ8WS40CQiqeFdxsR-Sg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Wed, May 20, 2026 at 3:16 PM solai v <solai(dot)cdac(at)gmail(dot)com> wrote:
>
> The patch applied successfully, and the build completed without issues.
> I verified that brin_index_check() is not available on an unpatched
> build,and after applying the patch and updating the amcheck extension
> to version 1.6 ,the function worked as expected.
> I also ran some basic BRIN index validation tests successfully.
Thank you for testing!
> One small thing I noticed during testing :after installing the patched
> build,I needed to run ALTER EXTENSION amcheck UPDATE before
> brin_index_check() became available.
>
IIUC it's possible if you use existing cluster with installed old
version of amcheck for testing. In that case it's ok that you need to
execute ALTER EXTENSION to update amcheck and apply patch changes.
Best regards,
Arseniy Mukhin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Karlsson | 2026-05-20 19:25:31 | Prevent setting NO INHERIT on partitioned not-null constraints |
| Previous Message | Maxime Schoemans | 2026-05-20 17:44:52 | Multi-Entry Indexing for GiST & SP-GiST |