From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Bagga, Rishu" <bagrishu(at)amazon(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SLRUs in the main buffer pool - Page Header definitions |
Date: | 2022-06-22 23:20:48 |
Message-ID: | 20220622232048.3ozc73nlds735z4v@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2022-06-22 19:12:14 -0400, Tom Lane wrote:
> "Bagga, Rishu" <bagrishu(at)amazon(dot)com> writes:
> > The current SLRU pages do not have any header, so there is a need to
> > create a new page header format for these. Our investigations revealed
> > that we need to:
>
> > 1. track LSN to ensure durability and consistency of all pages (for redo
> > and full page write purposes)
> > 2. have a checksum (for page correctness verification).
> > 3. A flag to identify if the page is a relational or BufferedObject
> > 4. Track version information.
>
> Isn't this a nonstarter from the standpoint of pg_upgrade?
We're rewriting some relation forks as part of pg_upgrade (visibility map
IIRC?), so rewriting an SLRU is likely not prohibitive - there's much more of
a limit to the SLRU sizes than the number and aggregate size of relation
forks.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2022-06-22 23:29:12 | Re: Amcheck verification of GiST and GIN |
Previous Message | Tom Lane | 2022-06-22 23:12:14 | Re: SLRUs in the main buffer pool - Page Header definitions |