Re: Lowering the default wal_blocksize to 4K

John Naylor <johncnaylorls@gmail.com>

From: John Naylor <johncnaylorls@gmail.com>
To: Andy Pogrebnoi <andrew.pogrebnoi@percona.com>
Cc: Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org, Heikki Linnakangas <hlinnaka@iki.fi>, Robert Haas <robertmhaas@gmail.com>, Thomas Munro <thomas.munro@gmail.com>, Matthias van de Meent <boekewurm+postgres@gmail.com>
Date: 2026-03-25T11:10:08Z
Lists: pgsql-hackers
On Wed, Feb 18, 2026 at 8:26 PM Andy Pogrebnoi
<andrew.pogrebnoi@percona.com> wrote:
> The Windows tests are failing on `Assert("check_GUC_init(hentry->gucvar)")` for wal_writer_flush_after [1]. It doesn't make much sense to me as both load- and C-value for the wal_writer_flush_after GUC are the same constant:

FWIW, they just started passing a couple days ago:

https://cirrus-ci.com/github/postgresql-cfbot/postgresql/cf%2F6490

-- 
John Naylor
Amazon Web Services



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. During online checkpoints, insert XLOG_CHECKPOINT_REDO at redo point.