Bruce Momjian wrote:
> KaiGai Kohei wrote:
> > lo_import() has an another prototype which takes second argument to
> > specify LOID. Isn't it available to restore a large object with
> > correct LOID? For example, lo_import('/etc/profile', 1234)
> I can't use that because the migration has already brought over the
> pg_largeobject file which has the data.
> > Or, if you intend to restore metadata in the second lo_import(),
> > ALTER LAEGE OBJECT and GRANT LARGE OBJECT enable to set up metadata
> > of a certain large object.
> Yes, that will work cleanly. The file might be large because I need a
> GRANT for every large object, but I suppose that is OK.
Uh, I tested pg_migrator and found a problem with this approach:
test=> select loid from pg_largeobject;
test=> grant all ON LARGE OBJECT 16385 to public;
ERROR: large object 16385 does not exist
I am wondering if the missing pg_largeobject_metadata row is causing
this, and again I have no way of creating one with the specified oid.
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
+ If your life is a hard drive, Christ can be your backup. +
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2009-12-13 03:18:46|
|Subject: Re: Row-Level Security|
|Previous:||From: Bruce Momjian||Date: 2009-12-13 02:15:42|
|Subject: Re: Largeobject Access Controls and pg_migrator|