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 1lNXk5-0005bf-2o for pgsql-hackers@arkaria.postgresql.org; Sat, 20 Mar 2021 09:17:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lNU1h-0001ei-HG for pgsql-hackers@arkaria.postgresql.org; Sat, 20 Mar 2021 05:19:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lNU1h-0001eb-69 for pgsql-hackers@lists.postgresql.org; Sat, 20 Mar 2021 05:19:53 +0000 Received: from mail-il1-x129.google.com ([2607:f8b0:4864:20::129]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lNU1d-0003en-Hd for pgsql-hackers@postgresql.org; Sat, 20 Mar 2021 05:19:52 +0000 Received: by mail-il1-x129.google.com with SMTP id m6so9932025ilh.6 for ; Fri, 19 Mar 2021 22:19:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=wa7G8Jt+enDKrJbkbl/MwagiE5g6BRDGCicHY3O6ny4=; b=by5eKU0RED9eTB7lYVRIvI0fjRqOXhS3eN10URjgs1ru0ehnquaVCgwgdVUudJEB6s 7RYPo0qamBYihBKWVOjLZ4CvWkZP0hWwOawSPtqeWu8xlbFEJcyW9jRLQr0oaifMvwmP neSudv+oDO2GCcnlCo5jZQ6bHnlV3dl47lEKAiaLg2Gq2Ylb0sLTeo0XQDWPCdNdi2k6 XlE/tfgttF2AgSFCDbWNYLt+8oZueuBwW6Ynq3yj19uE2Vt/n2Bu8xWaAXOGz+QuO7zG ev153SG3ze6zt+/ctNDD2Fp+VgclPt56LcgXwfyPMXU5gyiUo/CFw2v8SowFHWdQme00 mukg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=wa7G8Jt+enDKrJbkbl/MwagiE5g6BRDGCicHY3O6ny4=; b=InQi7Af2wpOgBJcjNne521DtNboAXZCF1QcUsogCy905s4MZVaXcCKFqfR03TjhxdC SfmtRgM9XeQSVWGnLQ6NkuPmxXn6Xc74pOMX0vMkzzh1txEIuQKwtuQDtmO4A2Q0c3K9 awQpokhW/wTlQCzvXq+TpueQ1wKbzZ771tkRsRCs1tO3yRPHCfhnz8G4JAn9tc9aN44d eG9scWHB3D2zQjFk5Ms3RPXNf6eNLBTbo3HfDldHpsN+M05CKX1YMhOaTZLIhqAA3SyG Zojodx02ueguOXv3rubTQTJcNXwRcK9rfJS6EXESZM+p4obFb7qS3FNCIZGqTmbAiRcR 7trA== X-Gm-Message-State: AOAM531ZH49nX6T9kFOckyCgUGVPZ5dxqbg5LOdVkA2ORGi23oFSH1M8 yQhgkAPBEXtBfhMTjAiP3qalxw== X-Google-Smtp-Source: ABdhPJxMXlc7EjDiDWxiu10HP11HHUwds3HwyM4e7k72a1Om8F4VRZUt8z/ge7lvVhvvW+iY3QcKgA== X-Received: by 2002:a92:dc03:: with SMTP id t3mr5337740iln.76.1616217587551; Fri, 19 Mar 2021 22:19:47 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id v15sm3753060ilm.77.2021.03.19.22.19.46 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Mar 2021 22:19:46 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 03A02800897; Sat, 20 Mar 2021 00:19:45 -0500 (CDT) Date: Sat, 20 Mar 2021 00:19:45 -0500 From: Justin Pryzby To: Mark Dilger Cc: Andrey Borodin , pgsql-hackers@postgresql.org Subject: Re: pglz compression performance, take two Message-ID: <20210320051945.GQ11765@telsasoft.com> References: <25991595-1848-4178-AA57-872B10309DA2@yandex-team.ru> <20201230043930.GG25152@telsasoft.com> <20210122024811.GE27167@telsasoft.com> <91F7608D-4800-49B8-B5EC-911AAF1BB069@enterprisedb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <91F7608D-4800-49B8-B5EC-911AAF1BB069@enterprisedb.com> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Mar 19, 2021 at 01:29:14PM -0700, Mark Dilger wrote: > Robert Haas just committed Dilip Kumar's LZ4 compression, bbe0a81db69bd10bd166907c3701492a29aca294. > > Is this pglz compression patch still relevant? How does the LZ4 compression compare on your hardware? I think it's still relevant, since many people may not end up with binaries --with-lz4 (I'm thinking of cloud providers). PGLZ is what existing data uses, and people may not want to/know to migrate to shiny new features, but they'd like it if their queries were 20% faster after upgrading without needing to. Also, Dilip's patch is only for TOAST compression, and pglz is also being used for wal_compression - Andrey has a short patch to implement lz4 for that: https://commitfest.postgresql.org/32/3015/ -- Justin