| From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | "Li, Yong" <yoli(at)ebay(dot)com>, "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, "Shyrabokau, Anton" <antons(at)ebay(dot)com>, "Debnath, Shawn" <sdn(at)ebay(dot)com> |
| Subject: | Re: Proposal to add page headers to SLRU pages |
| Date: | 2023-12-07 14:16:59 |
| Message-ID: | CAJ7c6TMUY=H2Hn=YbdYimk_NfVGq1QR9UhaPsE2Zd+8rgzdZMg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
> +1 to the idea to protect SLRUs from corruption. I'm slightly leaning towards the idea of separating checksums from data pages, but anyway this checksums are better than no checksums.
>
> On 7 Dec 2023, at 10:06, Li, Yong <yoli(at)ebay(dot)com> wrote:
>
> I am still working on patching the pg_upgrade. Just love to hear your thoughts on the idea and the current patch.
>
> FWIW you can take upgrade code from this patch [0] doing all the same stuff :)
Sounds like a half-measure to me. If we really want to go down this
rabbit hole IMO SLRU should be moved to shared buffers as proposed
elsewhere [1].
[1]: https://www.postgresql.org/message-id/EFAAC0BE-27E9-4186-B925-79B7C696D5AC@amazon.com
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-12-07 14:18:13 | Re: Configure problem when cross-compiling PostgreSQL 16.1 |
| Previous Message | David G. Johnston | 2023-12-07 14:11:08 | Re: Emitting JSON to file using COPY TO |