Re: adding 'zstd' as a compression algorithm

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: adding 'zstd' as a compression algorithm
Date: 2022-02-15 21:42:55
Message-ID: 20220215214255.cstkc4xpso7jq4j4@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2022-02-15 15:09:37 -0500, Robert Haas wrote:
> On Tue, Feb 15, 2022 at 2:54 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> > There's a difference between downloading a source tarball of 1.5x the size,
> > and 3x the decompression cost (made up numbers), because the cost of either is
> > not a relevant factor. I think basebackups are a different story.
>
> To be clear, I'm not saying that people shouldn't choose to adopt the
> new stuff. I'm just saying that many of them won't, for various
> reasons, including inertia. There may come a point when we want to
> make a push to remove obsolete stuff, but I think what is far more
> important right now is making the new stuff available.

I think well before removing stuff we should default to decent compression
algorithms. E.g. -Z/--compress should probably not continue to use gzip if
better things are available.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2022-02-15 21:43:10 Re: Observability in Postgres
Previous Message Andres Freund 2022-02-15 21:40:16 Re: Time to drop plpython2?