RE: [HACKERS] pg_dump & blobs - editable dump?

From: Peter Mount <petermount(at)it(dot)maidstone(dot)gov(dot)uk>
To: "'Philip Warner'" <pjw(at)rhyme(dot)com(dot)au>, Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org, Pavel(at)Janik(dot)cz
Subject: RE: [HACKERS] pg_dump & blobs - editable dump?
Date: 2000-07-12 14:32:10
Message-ID: 1B3D5E532D18D311861A00600865478CF1B07E@exchange1.nt.maidstone.gov.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Which is why having them on stdout is still a nice option to have. You can
pipe the lot through your favourite compressor (gzip, bzip2 etc) and
straight on to tape, or whatever.

I don't know why you would want them as separate files - just think what
would happen to directory search times!!

How about this as an idea:
* Option to dump sql to stdout and blobs to a designated file
* option to dump sql & blobs to stdout
* option to dump just sql to stdout
* option to dump just blobs to stdout

That way (depending on the database design), you could handle the sql &
blobs separately but still have everything backed up.

PS: Backups is formost on my mind at the moment - had an NT one blow up in
my face on Monday and it wasn't nice :-(

Peter

--
Peter Mount
Enterprise Support
Maidstone Borough Council
Any views stated are my own, and not those of Maidstone Borough Council

-----Original Message-----
From: Philip Warner [mailto:pjw(at)rhyme(dot)com(dot)au]
Sent: Wednesday, July 12, 2000 3:22 PM
To: Lamar Owen
Cc: pgsql-hackers(at)postgresql(dot)org; pgsql-general(at)postgresql(dot)org;
Pavel(at)Janik(dot)cz
Subject: Re: [HACKERS] pg_dump & blobs - editable dump?

At 10:13 12/07/00 -0400, Lamar Owen wrote:
>Philip Warner wrote:
>> My guess is that this will involve a plain text schema dump, followed by
>> all BLOBs in separate files, and a script to load them. To implement this
>> I'll obviosly need to be passed a directory/file location for the script
>> since I can't pipe seperate files to stdout.
>
>uuencode the blobs, perhaps, using a shar-like format?

For the human readable version, the request was to make it editable and
sendable to psql. As a result the BLOBs need to be in their binary format
OR psql needs to support BLOB import from stdin. As a first pass I was
hoping for the simple 'dump them into files' solution.

What I am confused by is what people actually want to do with a load of
BLOBs sitting in a directory; if there are specific needs, then I'd also
like to cater for them in the custom file formats.

----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/

Browse pgsql-general by date

  From Date Subject
Next Message Lamar Owen 2000-07-12 14:38:57 Re: [HACKERS] pg_dump & blobs - editable dump?
Previous Message Peter Mount 2000-07-12 14:25:24 RE: RE: [HACKERS] pg_dump & blobs - editable dump?

Browse pgsql-hackers by date

  From Date Subject
Next Message Lamar Owen 2000-07-12 14:38:57 Re: [HACKERS] pg_dump & blobs - editable dump?
Previous Message Zeugswetter Andreas SB 2000-07-12 14:29:53 AW: AW: update on TOAST status'