Re: Re: pg_dump and LOs (another proposal)

At 13:06 5/07/00 -0400, Tom Lane wrote:
>Shouldn't be a problem. For one thing, I can assure you there are no
>databases with 30,000 LOs in them ;-) --- the existing two-tables-per-LO
>infrastructure won't support it. (I think Denis Perchine has started

Eeek! Not so long ago I was going to use PG for a database will far more
than that many documents (mainly becuase of no backup, horrible storage
etc). Glad I didn't.

>> I'll also have to modify pg_restore to talk to the database directly (for
>> lo import). As a result I will probably send the entire script directly
>> from withing pg_restore. Do you know if comment parsing ('--') is done in
>> the backend, or psql?
>
>Both, I believe --- psql discards comments, but so will the backend.
>Not sure you really need to abandon use of psql, though.

Don't plan to abandon it, but I did plan to use lo_creat, lo_write to add
the LOs, and that requires no psql, I think. I want this utility to run
direct from tape, without lots of temp files.

I'll probably just have a new arg, --blobs, and another --db, which makes a
direct DB connection, and --blobs without --db will not be supported. Does
this sound OK?

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