From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Bagga, Rishu" <bagrishu@amazon.com>
cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Subject: Re: SLRUs in the main buffer pool - Page Header definitions
In-reply-to: <EFAAC0BE-27E9-4186-B925-79B7C696D5AC@amazon.com>
References: <EFAAC0BE-27E9-4186-B925-79B7C696D5AC@amazon.com>
Comments: In-reply-to "Bagga, Rishu" <bagrishu@amazon.com>
	message dated "Wed, 22 Jun 2022 21:06:29 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <3693889.1655939534.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Wed, 22 Jun 2022 19:12:14 -0400
Message-ID: <3693890.1655939534@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3693890.1655939534%40sss.pgh.pa.us>
Precedence: bulk

"Bagga, Rishu" <bagrishu@amazon.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?

			regards, tom lane