Re: Re: pg_dump and LOs (another proposal)

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel(dot)Janik(at)linux(dot)cz, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: pg_dump and LOs (another proposal)
Date: 2000-07-06 16:22:00
Message-ID: 3.0.5.32.20000707022200.026c5240@mail.rhyme.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 18:12 6/07/00 +0200, Peter Eisentraut wrote:
>Philip Warner writes:
>
>> I'll also have to modify pg_restore to talk to the database directly (for
>> lo import).
>
>psql has \lo_import.
>

This is true, but if there are 30000 blobs on an archive tape, I cant dump
them into /tmp and wait for the user to run the script. At the current time
pg_restore just sends a script to a file or stdout - it has no guarantee of
when a \lo_import command will be run, so dumping blobs into the same file
between lo_import calls would not be appropriate, since I am in effect
requiring a psql attachment.

So the plan is, in the first pass, to make BLOB restoration dependant on
having a DB connection.

Does this make more sense?

P.S. I have only half-written the lo dumping code, so this is all quite
open...

----------------------------------------------------------------
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 |/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 2000-07-06 16:24:29 Re: proposed improvements to PostgreSQL license
Previous Message The Hermit Hacker 2000-07-06 16:19:09 Re: [HACKERS] Re: Revised Copyright: is this more palatable?