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 1paljg-0006Hh-0p for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Mar 2023 23:01:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1palje-0004G8-BA for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Mar 2023 23:01:14 +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 1paljc-0004Fz-QU for pgsql-hackers@lists.postgresql.org; Fri, 10 Mar 2023 23:01:14 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1paljX-0004xL-1f for pgsql-hackers@lists.postgresql.org; Fri, 10 Mar 2023 23:01:12 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 662ED3200094; Fri, 10 Mar 2023 18:01:02 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 10 Mar 2023 18:01:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm1; t=1678489262; x=1678575662; bh=hR O5V6qZRNmN+JhJ0NZORdybzM00dq4+np3VjHifoCs=; b=XONelS9AFF+BXTz6Ij LoAUseArvMNpIbRLJGRtwpIe9UXgtdyiDZTQBPsuXejouJ/F1/GEpiGtZJS56cs8 iBoj+bkMoF8BZ1hqdhuaOla4SQCoOFnXrPmDDWKtnV84xTw68pxl3u7wb8jGzB7S szlhvKV3xNXKwbsIIUnsGa+yc6dOQqocySlr94YVf5vcGmC1pO32viHgubcyMNeh gi9jrqzpv1yaQEk7J1rbpGrD1h3llqtaRzzzdE3IHWNg4q/c4Mjat/4ap1GB6pYn ycybf6tpb1OfkL/lIVbRZkeuqsfEXb8DmOzWXK94oCFBLVu36q4e230jn5zhgc9R Q7Xg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1678489262; x=1678575662; bh=hRO5V6qZRNmN+ JhJ0NZORdybzM00dq4+np3VjHifoCs=; b=bwsMq4bn3tJl3FTvOHuj7Y6p1lBfz 3tqP7e2Q8MSVQBnmzDgvBLSI6jhm5RgcSzcggUlqNzzOh68DOanONbLU3YpnojH+ ox3aFdsnD0Ac8PESnhlbcpnvArBWCoaZ8LaBSPzyO7SrWxg7madZmb92QQKbvbjZ YTovHvmgLJHTyLKZTW0QnqSh2te7jdtNcMyXv4BGaqIiIwx70cjsyWa0YZhlSa7B MUCA+9JLVEIKGAZp5a9CSrf8DbSflJhELjDlBQ9oO5/BnivZvBigSeGnIJ46DN2x VJeiii6LV9C8R9iuKneZWUnTECh8XLS/7aoTQ1IKC3p4iJiFhTGjG6MpQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdduledgtdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdljedtmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredt tddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesph grqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepteelieefudffhffhtdetleeg geegfffhkeeuveetiefgudduvedutefggeeivdejnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiih ii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 10 Mar 2023 18:00:59 -0500 (EST) Date: Sat, 11 Mar 2023 08:00:55 +0900 From: Michael Paquier To: Justin Pryzby Cc: Tomas Vondra , gkokolatos@pm.me, shiy.fnst@fujitsu.com, pgsql-hackers@lists.postgresql.org, Rachel Heaton Subject: Re: Add LZ4 compression in pg_dump Message-ID: References: <20230224015115.GS1653@telsasoft.com> <20230225050214.GH1653@telsasoft.com> <20230225140553.GI1653@telsasoft.com> <20230227044910.GO1653@telsasoft.com> <09b37949-cfe5-29bb-cbb1-498ee5700b61@enterprisedb.com> <2f680c4f-0944-5fd0-2e39-8cd95ccb89f5@enterprisedb.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="9JB7mFMD0ngpKLVB" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --9JB7mFMD0ngpKLVB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 10, 2023 at 07:05:49AM -0600, Justin Pryzby wrote: > On Thu, Mar 09, 2023 at 06:58:20PM +0100, Tomas Vondra wrote: >> I'm a bit confused about the lz4 vs. lz4f stuff, TBH. If we switch to >> lz4f, doesn't that mean it (e.g. restore) won't work on systems that >> only have older lz4 version? What would/should happen if we take backup >> compressed with lz4f, an then try restoring it on an older system where >> lz4 does not support lz4f? >=20 > You seem to be thinking about LZ4F as a weird, new innovation I'm > experimenting with, but compress_lz4.c already uses LZ4F for its "file" > API. Note: we already use lz4 frames in pg_receivewal (for WAL) and pg_basebackup (bbstreamer). -- Michael --9JB7mFMD0ngpKLVB Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmQLtqcACgkQnvQgOdby QH1sOxAAg0V+wQ55Lkavp0IZLGLzs1GJwCsogEiyAswzkhrGn1mGlDFFKdeQJyC3 qNdLs2RiNYTjum9AYu2slLOY4aYDX9hcs1LQ54+SSLzZmk1hnKuBJUG09MF2hgkI 51vpQZvjVYj8kd1w7OPXq1Wnue6L3sdan15qCLajz/MTTAG8AUtMxuA7RCCIikaJ xmlriQgmOr9uetmmu2hOaiOe2+PTgJAvPs24mvQHzdSRNYXSakn4MADlrOdWPVEf nsqrYNXnj0VQQjndRoj2+79Y+5XPSJEx+qLNuv+Yiu8bET4m78V43Ynk1cdRb9Ki CFduoytccNsL9N6QPyCcJcoBfTto4eEq7mMIwgmbIeAyJ+wM5t3FMLTBMWjjbcSV AneiuL/D7/6iTKksULbJx8MARuci9MIPMrFwPMYVtvOHJcMGNf/SM7b6hoviq7oD 7fpsDlvJLqTFlF45Lp1TyTvoqsyMsSLeV1mOk4rnB5BDPbl7lfm3wWDgscT7GVmZ U6Ms0gNazUc+BwMJ4g+Z4z35YGQOthkdg/wBB33Avgjqj3lDNPu1jeZYch+NLvZh EfTQRKj0gb/p77Pv3Oh2tf50pqVbszvV2httdqJCT8FyaZ2Lye152WRd8U5K2lUT Lgi/px2hDqz3Mn187Agfkx+cDoErqADl38dQYlKOYezpSfNelLk= =JeLk -----END PGP SIGNATURE----- --9JB7mFMD0ngpKLVB--