KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
> We don't have any reason why still CASE ... WHEN and subquery for the given
> LOID. Right?
Ah, I see. I used your suggestion.
I applied the bug fixes. Our tools and contrib modules will always use
pg_largeobject_metadata instead of pg_largeobject to enumerate large objects.
I removed "GRANT SELECT (loid) ON pg_largeobject TO PUBLIC" from initdb
because users must use pg_largeobject_metadata.oid when they want to check
OIDs of large objects; If not, they could misjudge the existence of objects.
This is an unavoidable incompatibility unless we always have corresponding
tuples in pg_largeobject even for zero-length large objects.
NTT Open Source Software Center
In response to
pgsql-hackers by date
|Next:||From: Takahiro Itagaki||Date: 2009-12-14 00:55:48|
|Subject: Re: EXPLAIN BUFFERS|
|Previous:||From: Takahiro Itagaki||Date: 2009-12-14 00:26:23|
|Subject: Re: Largeobject Access Controls and pg_migrator|