public inbox for [email protected]  

help / color / mirror / Atom feed

From: Arseniy Mukhin <[email protected]>
To: PostgreSQL Hackers <[email protected]>
Subject: Re: amcheck support for BRIN indexes
Date: Fri, 1 Aug 2025 23:22:13 +0300
Message-ID: <CAE7r3ML7ua99HAHPkrwi5sFER+kt7_ZeARMn57JCqwKaWLhEng@mail.gmail.com> (raw)
In-Reply-To: <CAE7r3MJfwYQq9LqVYJDB85XwuXPD1GPsys8HvnqLQT-uB7Z-nw@mail.gmail.com>
References: <[email protected]>
	<[email protected]>
	<CAE7r3MJeqDSfic9pQedsRg3xg49q7=iq5PTuZNNNi7yqAw8dTw@mail.gmail.com>
	<[email protected]>
	<CAE7r3MLDcDjh5ieGS=UNtKVm6wG0mRRqdYGUEoKvsDoFp9PgRQ@mail.gmail.com>
	<CAE7r3MJfwYQq9LqVYJDB85XwuXPD1GPsys8HvnqLQT-uB7Z-nw@mail.gmail.com>

Hi,

On Tue, Jul 22, 2025 at 6:43 PM Arseniy Mukhin
<[email protected]> wrote:
>
> Hi,
>
> While reviewing gist amcheck patch [1] I realized that brin amcheck
> also must check if current snapshot is OK with index indcheckxmin (as
> btree, gist do it). Currently this check is contained in btree amcheck
> code, but other AMs need it for heapallindexed as well, so I moved it
> from btree to verify_common (0003 patch).

There was a compiler warning on CI, so there is a new version with the
fix (adds #include to verify_common).
I also moved it to PG19-2.


Best regards,
Arseniy Mukhin

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: amcheck support for BRIN indexes
  In-Reply-To: <CAE7r3ML7ua99HAHPkrwi5sFER+kt7_ZeARMn57JCqwKaWLhEng@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox