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 1pKlth-00065f-TD for pgsql-hackers@arkaria.postgresql.org; Wed, 25 Jan 2023 19:57:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pKltg-0007j7-QA for pgsql-hackers@arkaria.postgresql.org; Wed, 25 Jan 2023 19:57:28 +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 1pKltg-0007iy-HC for pgsql-hackers@lists.postgresql.org; Wed, 25 Jan 2023 19:57:28 +0000 Received: from mail-40134.protonmail.ch ([185.70.40.134]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pKlte-0007AS-I1 for pgsql-hackers@lists.postgresql.org; Wed, 25 Jan 2023 19:57:28 +0000 Date: Wed, 25 Jan 2023 19:57:18 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pm.me; s=protonmail3; t=1674676645; x=1674935845; bh=hX1IvhZvONIbLXmfuAhg4JyBeM0NbU+A1EcT3yGfAXo=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=Ob4ES9VPcdB1FeII1PV6og7WCx13FktLNFBnb1REBdurMrIqBTh+K+azaD+8XLGKX O3y5L7ddTnTyBhoag0os+YO1qLG8uoHm9zPsF7Trc8lQiJxVGt1dKaQ891KR0cWqnC 2AUIC384scx+uaOBvywAsFviUu3oJIvq9Y1rXk0BOf6KiS5Tg9MmH9BAxGnNJ+9k62 blpTy4ihBU+n8PiirYCD3b6OTnYyWgICgnvUKNSIVUclumW22agU9u7Foak+7Ui41q 75ZBDMFjtAltOwF4GTqbKBvzul5XdUlVzesRuEF3imd6+w62+Qx1uDIMJfMfkvv6YN FFhDH1pxyGp6w== To: Justin Pryzby From: gkokolatos@pm.me Cc: Tomas Vondra , Michael Paquier , pgsql-hackers@lists.postgresql.org, Rachel Heaton Subject: Re: Add LZ4 compression in pg_dump Message-ID: <4ZDVII-_kusch7xndcrTUt7OPSuQWQGX7n8rqp625Hdv6DijBjWZ38gjhxLSzPu8M_Dka-50eeKCiCU_dOdawwpv06dZtwGroYE9dHlIBLc=@pm.me> In-Reply-To: <20230125180020.GF22427@telsasoft.com> References: <20230123180014.GX13860@telsasoft.com> <20230125014203.GL13860@telsasoft.com> <-myGeDiZ-ePDRyi18026Iu2HTTfmwfjWaJn4OWJ2F3oglZUfJTOQ7FARPW7gYxE4vK3b0HpwYoiHR45nfOWReRvvJZfCBfJzPP5iJyn4muk=@pm.me> <20230125180020.GF22427@telsasoft.com> Feedback-ID: 6383013:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk ------- Original Message ------- On Wednesday, January 25th, 2023 at 7:00 PM, Justin Pryzby wrote: >=20 >=20 > On Wed, Jan 25, 2023 at 03:37:12PM +0000, gkokolatos@pm.me wrote: >=20 > While looking at this, I realized that commit 5e73a6048 introduced a > regression: >=20 > @@ -3740,19 +3762,24 @@ ReadHead(ArchiveHandle *AH) >=20 > - if (AH->compression !=3D 0) >=20 > - pg_log_warning("archive is compressed, but this installation does not s= upport compression -- no data will be available"); > + if (AH->compression_spec.algorithm =3D=3D PG_COMPRESSION_GZIP) >=20 > + pg_fatal("archive is compressed, but this installation does not support= compression"); >=20 > Before, it was possible to restore non-data chunks of a dump file, even > if the current build didn't support its compression. But that's now > impossible - and it makes the code we're discussing in RestoreArchive() > unreachable. Nice catch! Cheers, //Georgios > -- > Justin