Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nKa2I-0006os-Qc for pgsql-hackers@arkaria.postgresql.org; Thu, 17 Feb 2022 06:13:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nKa2H-0002tQ-Py for pgsql-hackers@arkaria.postgresql.org; Thu, 17 Feb 2022 06:13:01 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nKa2H-0002tH-D5 for pgsql-hackers@lists.postgresql.org; Thu, 17 Feb 2022 06:13:01 +0000 Received: from forwardcorp1p.mail.yandex.net ([77.88.29.217]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nKa2B-0006ZD-Va for pgsql-hackers@lists.postgresql.org; Thu, 17 Feb 2022 06:13:00 +0000 Received: from myt5-23f0be3aa648.qloud-c.yandex.net (myt5-23f0be3aa648.qloud-c.yandex.net [IPv6:2a02:6b8:c12:3e29:0:640:23f0:be3a]) by forwardcorp1p.mail.yandex.net (Yandex) with ESMTP id EBA782E0A90; Thu, 17 Feb 2022 09:12:51 +0300 (MSK) Received: from myt5-70c90f7d6d7d.qloud-c.yandex.net (myt5-70c90f7d6d7d.qloud-c.yandex.net [2a02:6b8:c12:3e2c:0:640:70c9:f7d]) by myt5-23f0be3aa648.qloud-c.yandex.net (mxbackcorp/Yandex) with ESMTP id OAMTthv2hK-CpHSCI72; Thu, 17 Feb 2022 09:12:51 +0300 X-Yandex-Fwd: 2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1645078371; bh=xo5EN+X5M4UbpQfsS29R51R7Z41uFGErqr2TSHbq6VE=; h=Message-Id:References:Date:Subject:Cc:To:In-Reply-To:From; b=EAcHxthvBaGFEw4EKRtrjaxP7VGQ5kfWqCEHi2OTop5Jl913QmUk1DDx2hmCIUjjJ a7AiA3wVi6X+k/5i6pWgMv8Yh65LREWv1ixraNta8GrRUZbqaDTpnbCXeIhvHsTKf0 VVQmUxiyLVJS8U0/LvjWrpo9S63xQehM27peB/WE= Authentication-Results: myt5-23f0be3aa648.qloud-c.yandex.net; dkim=pass header.i=@yandex-team.ru Received: from [IPv6:2a02:6b8:82:604:25d7:ad8:b199:d5b6] (unknown [2a02:6b8:82:604:25d7:ad8:b199:d5b6]) by myt5-70c90f7d6d7d.qloud-c.yandex.net (smtpcorp/Yandex) with ESMTPSA id osrgjUoaWn-CpHuOhhY; Thu, 17 Feb 2022 09:12:51 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) Subject: Re: adding 'zstd' as a compression algorithm From: Andrey Borodin In-Reply-To: Date: Thu, 17 Feb 2022 11:12:50 +0500 Cc: PostgreSQL Hackers Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Robert Haas X-Mailer: Apple Mail (2.3608.120.23.2.7) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > 15 =D1=84=D0=B5=D0=B2=D1=80. 2022 =D0=B3., =D0=B2 23:20, Robert Haas = =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0)= : >=20 > 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.=