Re: WAL_LOG CREATE DATABASE strategy broken for non-standard page layouts

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: surya poondla <suryapoondla4(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Rogers Wang <rogers(dot)ww(at)qq(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: WAL_LOG CREATE DATABASE strategy broken for non-standard page layouts
Date: 2026-11-16 17:37:22
Message-ID: CAAKRu_ZjMXFvH5VJbXVDoro6HtrqpdsmFb4=CqRRHtiax_xk9g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 11, 2026 at 6:14 PM surya poondla <suryapoondla4(at)gmail(dot)com> wrote:
>
> A minor optional suggestion, isnt($primary_visibility_map, '', ...) only checks that rows come back. If VACUUM (FREEZE) ever left the bits
> unset, both nodes would show f|f and the test would pass without testing anything. Checking that the primary has at least one
> all-frozen page would guard against that.

Okay, I did this in v3.

- Melanie

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tristan Partin 2026-11-16 17:49:07 Re: compiler attribute alloc_size
Previous Message Melanie Plageman 2026-11-16 17:35:22 Re: WAL_LOG CREATE DATABASE strategy broken for non-standard page layouts