From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: broken reading on standby (PostgreSQL 16.2) |
Date: | 2024-04-25 07:06:20 |
Message-ID: | CAFj8pRA6oEV2diydiuWyKGQ-jxnv46==hjbPjXiyMqMYHrwNag@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
čt 25. 4. 2024 v 8:52 odesílatel Andrey M. Borodin <x4mmm(at)yandex-team(dot)ru>
napsal:
>
>
> > On 25 Apr 2024, at 11:12, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> >
> > yesterday, I had to fix strange issue on standby server
>
> It’s not just broken reading, if this standby is promoted in HA cluster -
> this would lead to data loss.
> Recently I’ve observed some lost heap updates ofter OOM-ing cluster on
> 14.11. This might be unrelated most probably, but I’ll post a link here,
> just in case [0]. In February and March we had 3 clusters with similar
> problem, and this is unusually big number for us in just 2 months.
>
> Can you check LSN of blocks with corrupted tuples with pageinpsect on
> primary and on standby? I suspect they are frozen on primary, but have
> usual xmin on standby.
>
Unfortunately, I have not direct access to backup, so I am not able to test
it. But VACUUM FREEZE DISABLE_PAGE_SKIPPING on master didn't help
>
>
> Best regards, Andrey Borodin.
>
> [0]
> https://www.postgresql.org/message-id/flat/67EADE8F-AEA6-4B73-8E38-A69E5D48BAFE%40yandex-team.ru#1266dd8b898ba02686c2911e0a50ab47
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2024-04-25 07:07:54 | Re: Experiments with Postgres and SSL |
Previous Message | Bharath Rupireddy | 2024-04-25 06:59:18 | Re: Add missing ConditionVariableCancelSleep() in slot.c |