X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id D586F9FB201 for ; Wed, 12 Jul 2006 23:53:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 47695-03 for ; Wed, 12 Jul 2006 23:53:28 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 2B2559FB200 for ; Wed, 12 Jul 2006 23:53:28 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k6D2rPk0001821; Wed, 12 Jul 2006 22:53:26 -0400 (EDT) To: "Steve McWilliams" cc: pgsql-performance@postgresql.org Subject: Re: size of pg_dump files containing bytea values In-reply-to: <3985.10.1.1.126.1152729387.squirrel@portal.emprisanetworks.com> References: <3985.10.1.1.126.1152729387.squirrel@portal.emprisanetworks.com> Comments: In-reply-to "Steve McWilliams" message dated "Wed, 12 Jul 2006 14:36:27 -0400" Date: Wed, 12 Jul 2006 22:53:25 -0400 Message-ID: <1820.1152759205@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/125 X-Sequence-Number: 19985 "Steve McWilliams" writes: > I notice that non-printables in bytea values are being spit out by pg_dump > using escaped octet sequences even when the "-Fc" option is present > specifying use of the custom binary output format rather than plain text > format. This bloats the size of bytea values in the dump file by a factor > of 3+ typically. No, because the subsequent compression step should buy back most of that. regards, tom lane