Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qtpOc-00E6Ze-Ej for pgsql-bugs@arkaria.postgresql.org; Fri, 20 Oct 2023 13:18:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qtpOZ-001lDX-9l for pgsql-bugs@arkaria.postgresql.org; Fri, 20 Oct 2023 13:18:31 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qtpOX-001l8H-TB for pgsql-bugs@lists.postgresql.org; Fri, 20 Oct 2023 13:18:31 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qtpOU-001Qv3-Vk for pgsql-bugs@lists.postgresql.org; Fri, 20 Oct 2023 13:18:29 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id A4F4132009D8; Fri, 20 Oct 2023 09:18:23 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Fri, 20 Oct 2023 09:18:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1697807903; x= 1697894303; bh=ZA7U0/bdw90tNOMNzrDIiEH9MNoLW2nhSHMwvsOiwuw=; b=p TPtYHQkMs/ANIA12//kp+Nhs12sWPaj7Lpg3iC3qV8T2g+ItxzeKNh+UUL7ns3tA br7Xa1fBocI0kEtHgerwfUN1aMuUUQa9CHtQIUTEUPH67bmACRN4x+JBVN6ELI9L IFe0yaM60/vflG/oZL7vPHfGxpz5un5CXtG/3Lsm7meV1BraJGxXb8E37/n17abF N95DB65rm6zwCQSYGeXjOjRTvI/pF66hYJOgRlji6NjOGTb4FsNj7XRD9Xfnd6X3 x/s9DpF6GA0uV38t5w2bOYvlYoS+jDn50WD1nUviiN8kOIl+7XhwPrJBNr4ZUaAL mr481E3SNV0LBBFyzszYw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrjeekgdeiudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvvefukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpedvkedtffduffdtffffheffhfejjefhgfeiueeukeejkeff gfdufffhudffffeuveenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtohhmne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhh vghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 20 Oct 2023 09:18:22 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alvh.no-ip.org; s=schmee; t=1697807899; bh=wquR+ZV4uVdpJ4dJFD+vAJWY+Z0cOzanoanNTCMsmUI=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=LNo7wuCw0MXoTUMB0PhH+2KAv2Co76itffm5zF9O3zQ/3FxRVeqsJgyFU1Y8K3wEL VCa9UG4PDLqCx/Dgr26s+44Ubjj43kk+L8I/BHHUj3F81sDOViglFXj9v9gw5ehNgH 6DJPTvqy5NnmOgTtP6hzA2BgKGFBzn4d4qmteGdwBAfSDHkPINmJ1/SOsZ19mSWvKi w+GbPD18doMl09rjQITbzfSfVtu9997PNuizr4mYXlWykboqIyy4qaLuUdMH9o2JA1 HwjRUUfGoorwfoDOV7tG6fMJ0aoAWNBhk6qte9q3SA4GZiM6VD4flag88ZuqJtrytf 89+3ya5Fo/+1A== Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id EDB2DD8; Fri, 20 Oct 2023 15:18:19 +0200 (CEST) Date: Fri, 20 Oct 2023 15:18:19 +0200 From: Alvaro Herrera To: Janning Vygen Cc: pgsql-bugs@lists.postgresql.org Subject: Re: slow pg_dump with bytea Message-ID: <202310201318.ukcklynpe5bq@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1325559b-6a40-411d-a1ab-1e1162e3722b@kicktipp.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-Oct-20, Janning Vygen wrote: > So maybe you can fix it by changing the pg_dump process to not compress any > bytea data. The problem with this idea is that the compression applies to the whole data stream. The backup format doesn't allow to compress some columns and not others. Doing that would require a lot of changes to pg_dump. Maybe a workable idea would be to allow excluding individual tables from being compressed. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "El hombre nunca sabe de lo que es capaz hasta que lo intenta" (C. Dickens)