From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: pglz compression performance, take two
Date: Sat, 26 Dec 2020 13:07:41 -0500
Message-ID: <1292319.1609006061@sss.pgh.pa.us> (raw)
In-Reply-To: <18a39267-341b-0424-2b05-9a0f54e55a9d@enterprisedb.com>
References: <FEF3DC5E-4BC4-44E1-8DEB-DADC67046FE3@yandex-team.ru>
<D75ABE30-2AAA-47DB-A89F-665E03BAAD2A@yandex-team.ru>
<25991595-1848-4178-AA57-872B10309DA2@yandex-team.ru>
<18a39267-341b-0424-2b05-9a0f54e55a9d@enterprisedb.com>
Tomas Vondra <tomas.vondra@enterprisedb.com> writes:
> On 12/26/20 8:06 AM, Andrey Borodin wrote:
>> I'm still in doubt should I register this patch on CF or not. I'm willing to work on this, but it's not clear will it hit PGv14. And I hope for PGv15 we will have lz4 or something better for WAL compression.
> I'd suggest registering it, otherwise people are much less likely to
> give you feedback. I don't see why it couldn't land in PG14.
Even if lz4 or something else shows up, the existing code will remain
important for TOAST purposes. It would be years before we lose interest
in it.
regards, tom lane
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: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, tomas.vondra@enterprisedb.com, x4mmm@yandex-team.ru
Subject: Re: pglz compression performance, take two
In-Reply-To: <1292319.1609006061@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox