Re: Lowering the default wal_blocksize to 4K
Andy Pogrebnoi <andrew.pogrebnoi@percona.com>
From: Andy Pogrebnoi <andrew.pogrebnoi@percona.com>
To: Andres Freund <andres@anarazel.de>
Cc: 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-02-16T08:19:21Z
Lists: pgsql-hackers
Attachments
- 0001-Change-wal_blocksize-default-to-4KB.patch (application/octet-stream) patch 0001
- (unnamed) (text/plain)
> On Feb 16, 2026, at 10:04, Andy Pogrebnoi <andrew.pogrebnoi@percona.com> wrote: > > Hello, > > >> On Oct 10, 2023, at 02:08, Andres Freund <andres@anarazel.de> wrote: >> >> Hi, >> >> I've mentioned this to a few people before, but forgot to start an actual >> thread. So here we go: >> >> I think we should lower the default wal_blocksize / XLOG_BLCKSZ to 4096, from >> the current 8192. > > I prepared a patch in case we want to move with the default 4kb XLOG_BLCKSZ. I forgot to include the patch in the prev message — Cheers, Andy
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
During online checkpoints, insert XLOG_CHECKPOINT_REDO at redo point.
- afd12774ae89 17.0 landed