From: Jim Nasby <jnasby@pervasive.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Nicola Mauri <Nicola.Mauri@saga.it>
Cc: pgsql-admin@postgresql.org
Subject: Re: Dump size bigger than pgdata size?
Date: Thu, 22 Jun 2006 20:58:14 -0500
Message-ID: <5F1778F3-ACEA-44C3-B895-D651EF62CBBA@pervasive.com> (raw)
In-Reply-To: <11486.1150909222@sss.pgh.pa.us>
References: <OF406B6E88.F5B37D76-ONC1257194.004D5FAC-C1257194.004F9F44@saga.it>
<11486.1150909222@sss.pgh.pa.us>
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...
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: jnasby@pervasive.com, tgl@sss.pgh.pa.us, Nicola.Mauri@saga.it
Subject: Re: Dump size bigger than pgdata size?
In-Reply-To: <5F1778F3-ACEA-44C3-B895-D651EF62CBBA@pervasive.com>
References: <OF406B6E88.F5B37D76-ONC1257194.004D5FAC-C1257194.004F9F44@saga.it> <11486.1150909222@sss.pgh.pa.us> <5F1778F3-ACEA-44C3-B895-D651EF62CBBA@pervasive.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox