From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 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-05 16:54:27 |
Message-ID: | 3.0.5.32.20000706025427.00cd7100@mail.rhyme.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 11:09 5/07/00 -0400, Tom Lane wrote:
>Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
>> Having now flirted with recreating BLOBs (and even DBs) with matching OIDs,
>> I find myself thinking it's a waste of effort for the moment. A modified
>> version of the system used by Pavel Janik in pg_dumplo may be substantially
>> more reliable than my previous proposal:
>
>I like this a lot better than trying to restore the original OIDs. For
>one thing, the restore-original-OIDs idea cannot be made to work if what
>we want to do is load additional tables into an existing database.
>
The thing that bugs me about this if for 30,000 rows, I do 30,000 updates
after the restore. It seems *really* inefficient, not to mention slow.
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?
----------------------------------------------------------------
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 |/
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2000-07-05 16:56:30 | update on TOAST status |
Previous Message | Jeffery Collins | 2000-07-05 16:52:04 | Re: update on TOAST status |