Re: Re: pg_dump and LOs (another proposal)

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
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-07 16:15:48
Message-ID: Pine.LNX.4.21.0007062347420.4191-100000@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Philip Warner writes:

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

I don't understand. How else would you restore a large object if not using
libpq's lo_import() call?

--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2000-07-07 16:15:54 Re: Re: pg_dump and LOs (another proposal)
Previous Message Tom Lane 2000-07-07 16:03:51 Re: update on TOAST status'