Bruce Momjian wrote:
> KaiGai Kohei wrote:
> > > What happens when
> > > there is no entry in pg_largeobject_metadata for a specific row?
> > In this case, these rows become orphan.
> > So, I think we need to create an empty large object with same LOID on
> > pg_migrator. It makes an entry on pg_largeobject_metadata without
> > writing anything to the pg_largeobject.
> > I guess rest of migrations are not difference. Correct?
> Agreed. I have modified pg_migrator with the attached patch which
> creates a script that adds default permissions for all large object
Oops, seem like I have a problem in getting pg_migrator to populate
test=> select lo_import('/etc/profile');
test=> select lo_import('/etc/profile.env');
test=> select oid,* from pg_largeobject_metadata;
oid | lomowner | lomacl
16385 | 10 |
16386 | 10 |
You might remember that INSERT cannot set the oid of a row, so I don't
see how pg_migrator can migrate this? Is there a reason we used 'oid'
in pg_largeobject_metadata but 'lobj' in pg_largeobject? Why did't we
add the lomowner and lomacl columns to pg_largeobject?
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: KaiGai Kohei||Date: 2009-12-13 01:55:29|
|Subject: Re: Largeobject Access Controls and pg_migrator|
|Previous:||From: Bruce Momjian||Date: 2009-12-13 01:24:20|
|Subject: Re: Largeobject Access Controls (r2460)|