Re: Dump size bigger than pgdata size?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jim Nasby <jnasby(at)pervasive(dot)com>
Cc: "Nicola Mauri" <Nicola(dot)Mauri(at)saga(dot)it>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Dump size bigger than pgdata size?
Date: 2006-06-23 02:39:06
Message-ID: 10263.1151030346@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Jim Nasby <jnasby(at)pervasive(dot)com> 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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Jeff Frost 2006-06-23 02:51:49 Re: strange fsm issues
Previous Message Jim Nasby 2006-06-23 02:24:15 Re: strange fsm issues