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 599C59FB2E0 for ; Thu, 13 Jul 2006 13:31:09 -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 19995-01 for ; Thu, 13 Jul 2006 13:31:06 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from stark.xeocode.com (stark.xeocode.com [216.58.44.227]) by postgresql.org (Postfix) with ESMTP id 18D679FA31F for ; Thu, 13 Jul 2006 13:31:05 -0300 (ADT) Received: from localhost ([127.0.0.1] helo=stark.xeocode.com) by stark.xeocode.com with smtp (Exim 3.36 #1 (Debian)) id 1G145T-0000Em-00; Thu, 13 Jul 2006 12:30:51 -0400 To: Tom Lane Cc: "Steve McWilliams" , pgsql-performance@postgresql.org Subject: Re: size of pg_dump files containing bytea values References: <3985.10.1.1.126.1152729387.squirrel@portal.emprisanetworks.com> <1820.1152759205@sss.pgh.pa.us> In-Reply-To: <1820.1152759205@sss.pgh.pa.us> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 13 Jul 2006 12:30:50 -0400 Message-ID: <87k66hii11.fsf@stark.xeocode.com> Lines: 17 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/132 X-Sequence-Number: 19992 Tom Lane writes: > "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. Didn't byteas used to get printed as hex? Even in psql they're now being printed in the escaped octet sequence. When did this change? -- greg