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-08 04:06:12
Message-ID: ascWtOql0xSrFetW@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 08, 2026 at 08:53:17AM +0500, Andrey Borodin wrote:
> 0001 reuses the compression context on WAL insertion. I restored the
> fallback to an uncompressed image if context allocation fails, rather
> than risking a PANIC in a critical section.

Thanks. Will look at this one next, even if I don't think that I will
have much to say. I was wondering about some micro-benchmarking to
reduce the amount of noise to zero, even if that would just be testing
an equivalent of native zstd...
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Manu 2026-10-08 04:24:52 Re: Fix doc: explanation of how postgres works when OOM killer is invoked
Previous Message Amit Langote 2026-10-08 03:58:00 Re: Two more RI fast-path issues