X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id CCC939FA5E6 for ; Thu, 22 Jun 2006 23:39:14 -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 16609-01 for ; Thu, 22 Jun 2006 23:39:08 -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 CC4A09FA2F4 for ; Thu, 22 Jun 2006 23:39:08 -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 k5N2d6wn010264; Thu, 22 Jun 2006 22:39:06 -0400 (EDT) To: Jim Nasby cc: "Nicola Mauri" , pgsql-admin@postgresql.org Subject: Re: Dump size bigger than pgdata size? In-reply-to: <5F1778F3-ACEA-44C3-B895-D651EF62CBBA@pervasive.com> References: <11486.1150909222@sss.pgh.pa.us> <5F1778F3-ACEA-44C3-B895-D651EF62CBBA@pervasive.com> Comments: In-reply-to Jim Nasby message dated "Thu, 22 Jun 2006 20:58:14 -0500" Date: Thu, 22 Jun 2006 22:39:06 -0400 Message-ID: <10263.1151030346@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/207 X-Sequence-Number: 22169 Jim Nasby writes: > On Jun 21, 2006, at 12:00 PM, Tom Lane wrote: >> This could be avoided by using COPY BINARY format, but I don't see any >> very nice way to do that in the context of pg_dump --- it needs to >> intermix COPY data with SQL commands ... > Would the tar or custom format allow for this? IIRC, at least tar > puts all the copied data into separate files... Well, you could sorta do that, but the case that would stop working is pg_restore output to a plain text SQL script (and related issues such as the ability to use the feature in the context of pg_dumpall). Having just gotten done fixing similar inconsistencies in pg_dump/pg_restore for BLOBs, I'm not eager to re-introduce 'em for COPY BINARY ... regards, tom lane