Re: Compression of bigger WAL records

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: Japin Li <japinli(at)hotmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Compression of bigger WAL records
Date: 2026-10-14 07:43:41
Message-ID: as8yrSp5RLTLw0qj@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 08, 2026 at 11:20:35AM +0500, Andrey Borodin wrote:
> This is still only a hypothesis. My benchmark hosts are unavailable today
> due to data center maintenance. When they are back, I can measure context
> creation and library versions.

Thanks. I have been playing with some of my cases and quickly
measured a 6% improvement of my VACUUM FULL workload from upthread,
and a lot less CPU getting used. In short, applied the WAL insert
part.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nikhil Sontakke 2026-10-14 07:47:55 Re: DDL deparse
Previous Message Steven Niu 2026-10-14 07:38:09 Re: Incorrect argument passed to buffer_readv_encode_error()