| 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 09:07:13 |
| Message-ID: | CAFj8pRBA5-rVO7+CuesLVFXASzt7gADhHbHDAg6VVsTBFNNznA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
čt 25. 4. 2024 v 10:52 odesílatel Andrey M. Borodin <x4mmm(at)yandex-team(dot)ru>
napsal:
>
>
> > On 25 Apr 2024, at 12:06, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> >
> > 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
> >
>
> If Primary considers all freezable tuples frozen, but a standby does not,
> "disable page skipping" won't change anything. Primary will not emit WAL
> record to freeze tuples again.
>
yes, this is possible. I git just info about broken xmin, so I expected
broken xlog, and then I first tested FREEZE
>
>
> Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2024-04-25 10:16:25 | Re: cataloguing NOT NULL constraints |
| Previous Message | vignesh C | 2024-04-25 08:58:40 | Improving the latch handling between logical replication launcher and worker processes. |