Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cwmDr-0004fD-L3 for pgsql-admin@arkaria.postgresql.org; Sat, 08 Apr 2017 08:59:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cwmDp-0001Xl-UZ for pgsql-admin@arkaria.postgresql.org; Sat, 08 Apr 2017 08:59:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cwmC4-0006l3-TF for pgsql-admin@postgresql.org; Sat, 08 Apr 2017 08:58:04 +0000 Received: from mail.am-soft.de ([83.218.36.120]) by magus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cwmC2-0001kZ-1w for pgsql-admin@postgresql.org; Sat, 08 Apr 2017 08:58:04 +0000 Received: from tschoening-nb.fritz.box (dslb-094-222-226-104.094.222.pools.vodafone-ip.de [94.222.226.104]) by mail.am-soft.de (Postfix) with ESMTP id 6DF38EEDCA for ; Sat, 8 Apr 2017 10:57:55 +0200 (CEST) Date: Sat, 8 Apr 2017 10:58:02 +0200 From: =?utf-8?Q?Thorsten_Sch=C3=B6ning?= Organization: AM-SoFT IT-Systeme Message-ID: <329300973.20170408105802@am-soft.de> To: pgsql-admin@postgresql.org Subject: pg_dump with custom format without compression MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Hi all, I'm using pg_dump with custom format "c" on some databases containing already compressed large binaries, like Zip, compressed PDF etc. So I don't benefit of the compression of format "c" much, but creating a dump takes about twice as much time compared to uncompressed format "t". Is there any way to use format "c" without any compression, so I get somewhat the same processing time like with format "t"? =46rom the docs it sounds that format "c" is the most flexible when it comes to restore and I would simply like to keep all the options it provides, just in case. So if not compression is only possible with "t", I might as well decide to use that and live with its theoretical shortcomings on restore. Thanks! Mit freundlichen Gr=C3=BC=C3=9Fen, Thorsten Sch=C3=B6ning --=20 Thorsten Sch=C3=B6ning E-Mail: Thorsten.Schoening@AM-SoFT.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Gesch=C3=A4ftsf=C3=BChrer: Andreas Muchow --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin