Re: Non-replayable WAL records through overflows and >MaxAllocSize lengths

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Matthias van de Meent <boekewurm+postgres@gmail.com>

Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Andres Freund <andres@anarazel.de>, Ian Lawrence Barwick <barwick@gmail.com>, Heikki Linnakangas <hlinnaka@iki.fi>, David Zhang <david.zhang@highgo.ca>, Robert Haas <robertmhaas@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2023-04-07T06:05:17Z

Lists: pgsql-hackers

On Fri, Apr 07, 2023 at 08:59:22AM +0900, Michael Paquier wrote:
> Okay, cool!

Done this one with 8fcb32d.
--
Michael

Commits

Add more protections in WAL record APIs against overflows
- 8fcb32db98ed 16.0 landed
Add overflow protection for block-related data in WAL records
- ffd1b6bb6f8a 16.0 landed
Change internal RelFileNode references to RelFileNumber or RelFileLocator.
- b0a55e43299c 16.0 cited
Revamp the WAL record format.
- 2c03216d8311 9.5.0 cited