Re: Compression of bigger WAL records

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Compression of bigger WAL records
Date: 2025-01-13 05:14:24
Message-ID: ECCAD8F2-032D-42FE-B60D-0D6EB0423FF2@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi! Thanks for looking into this!

> On 12 Jan 2025, at 23:36, Kirill Reshke <reshkekirill(at)gmail(dot)com> wrote:
>
> initdb fails when configured with --without-zstd

Yes, the patch is intended to demonstrate improvement when using Zstd.

> On 12 Jan 2025, at 17:43, Andrey M. Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
>
> WAL_DEBUG and wal_compression are enabled for debugging purposes. Of course, I do not propose to turn them on by default.

And this does not work well --without-zstd.

> Also pg_waldump fails with
>
> ```
> corrupted size vs. prev_size
> Aborted (core dumped)
> ```

I’ll fix that, thanks!
Also seems like I forgot to bump WAL_FILE_MAGIC…

What do you think about proposed approach?

Best regards, Andrey Borodin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2025-01-13 06:36:26 Re: Conflict detection for update_deleted in logical replication
Previous Message Robert Treat 2025-01-13 04:51:50 Re: Question about behavior of deletes with REPLICA IDENTITY NOTHING