Re: Do not check unlogged indexes on standby

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Do not check unlogged indexes on standby
Date: 2019-08-12 22:36:23
Message-ID: CAH2-WzkjPUdZyYs+Z2kH5Go05ZFFk68q7jmUQ6asXX_JvixcCQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 12, 2019 at 2:58 AM Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
> BTW I really want to enable rightlink-leftlink invariant validation on standby..

That seems very hard. My hope was that bt_check_index() can detect the
same problem a different way. The bt_right_page_check_scankey()
cross-page check (which needs nothing more than an AccessShareLock)
will often detect such problems, because the page image itself will be
totally wrong in some way.

I'm guessing that you have direct experience with that *not* being
good enough, though. Can you share further details? I suppose that
bt_right_page_check_scankey() helps with transposed pages, but doesn't
help so much when you have WAL-level inconsistencies.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2019-08-12 23:15:42 Re: pg_stat_replication lag fields return non-NULL values even with NULL LSNs
Previous Message Bruce Momjian 2019-08-12 22:32:26 Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)