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 55FE29FB1C3 for ; Thu, 13 Jul 2006 14:42:57 -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 31993-03 for ; Thu, 13 Jul 2006 14:42:48 -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 43FAB9FB1B7 for ; Thu, 13 Jul 2006 14:42:48 -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 k6DHggYa016772; Thu, 13 Jul 2006 13:42:42 -0400 (EDT) To: Greg Stark cc: "Steve McWilliams" , pgsql-performance@postgresql.org Subject: Re: size of pg_dump files containing bytea values In-reply-to: <87k66hii11.fsf@stark.xeocode.com> References: <3985.10.1.1.126.1152729387.squirrel@portal.emprisanetworks.com> <1820.1152759205@sss.pgh.pa.us> <87k66hii11.fsf@stark.xeocode.com> Comments: In-reply-to Greg Stark message dated "13 Jul 2006 12:30:50 -0400" Date: Thu, 13 Jul 2006 13:42:41 -0400 Message-ID: <16771.1152812561@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/134 X-Sequence-Number: 19994 Greg Stark writes: > Didn't byteas used to get printed as hex? No, not that I recall. I don't have anything older than 7.0 running, but it behaves the same as now: play=> select 'xyz\\001'::bytea; ?column? ---------- xyz\001 (1 row) play=> regards, tom lane