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

From: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Non-replayable WAL records through overflows and >MaxAllocSize lengths
Date: 2022-03-15 22:57:48
Message-ID: CAEze2WiNGUmxccd2bUywtLjHKSJTqpx=frcB1pOGhbs0CRkq9Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Apart from registering this in CF 2022-07 last Friday, I've also just
added this issue to the Open Items list for PG15 under "Older bugs
affecting stable branches"; as a precaution to not lose track of this
issue in the buzz of the upcoming feature freeze.

-Matthias

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2022-03-15 23:00:11 Re: document the need to analyze partitioned tables
Previous Message Nathan Bossart 2022-03-15 22:44:39 Re: Estimating HugePages Requirements?