public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andrey Borodin <[email protected]>
To: Robert Haas <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: adding 'zstd' as a compression algorithm
Date: Thu, 17 Feb 2022 11:12:50 +0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+TgmoatQKGd+8SjcV+bzvw4XaoEwminHjU83yG12+NXtQzTTQ@mail.gmail.com>
References: <CA+TgmoatQKGd+8SjcV+bzvw4XaoEwminHjU83yG12+NXtQzTTQ@mail.gmail.com>



> 15 февр. 2022 г., в 23:20, Robert Haas <[email protected]> написал(а):
> 
> Anyway, those are my thoughts. What are yours?

+1 for adding Zstd everywhere. Quite similar patches are already a part of "libpq compression" and "zstd for pg_dump" commitfest entries, so pushing this will simplify those entries IMV.

Also I like the idea of defaulting FPI compression to lz4 and adding Zstd as wal_compression option.
I don't think Zstd is obvious choice for default FPI compression: there are HW setups when disks are almost as fast as RAM. In this case lz4 can improve performance, while Zstd might make things slower.

Thanks!

Best regards, Andrey Borodin.

view thread (2+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: adding 'zstd' as a compression algorithm
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox