pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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: Tue, 27 Jun 2006 19:15:39 -0500
Message-ID: <219F801D-2039-4729-8CEC-B9EEC0C2F3BF@pervasive.com> (raw)
In-Reply-To: <10263.1151030346@sss.pgh.pa.us>
References: <OF406B6E88.F5B37D76-ONC1257194.004D5FAC-C1257194.004F9F44@saga.it>
	<11486.1150909222@sss.pgh.pa.us>
	<5F1778F3-ACEA-44C3-B895-D651EF62CBBA@pervasive.com>
	<10263.1151030346@sss.pgh.pa.us>

On Jun 22, 2006, at 9:39 PM, Tom Lane wrote:
> Jim Nasby <jnasby@pervasive.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 ...

Yeah, but how many people actually do that anyway? I can't really  
come up with a use-case for it, and I'm pretty sure there's other  
gains to be had by turning custom or tar format into more of a  
'binary dump'. For one thing, that should ease the need to run the  
newer version of pg_dump when upgrading (if we put the requisite  
brains into pg_restore).

I suppose we could put support in pg_restore to convert between  
BINARY and escaped as needed; or just disallow pg_restore from  
dumping SQL if there's binary data (maybe have it include copy  
statements that reference the specific 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





view thread (7+ messages)

Message-ID: <219F801D-2039-4729-8CEC-B9EEC0C2F3BF@pervasive.com>
Permalink:  ../219F801D-2039-4729-8CEC-B9EEC0C2F3BF@pervasive.com/
Also on:    postgresql.org/message-id/219F801D-2039-4729-8CEC-B9EEC0C2F3BF@pervasive.com

 · 

reply

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: <219F801D-2039-4729-8CEC-B9EEC0C2F3BF@pervasive.com>
  References: <OF406B6E88.F5B37D76-ONC1257194.004D5FAC-C1257194.004F9F44@saga.it> <11486.1150909222@sss.pgh.pa.us> <5F1778F3-ACEA-44C3-B895-D651EF62CBBA@pervasive.com> <10263.1151030346@sss.pgh.pa.us> <219F801D-2039-4729-8CEC-B9EEC0C2F3BF@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