Tom Lane wrote: > KaiGai Kohei <kai...@ak.jp.nec.com> writes: >> I rebased the largeobject access controls patch to the CVS HEAD >> because of the patch confliction to the default ACL patch. > > Quick comment on this --- I think that using a syscache for large > objects is probably not a good idea. There is no provision in the > catcache code for limiting the cache size anymore, and that means that > anybody who touches a large number of large objects is going to blow out > memory. We removed the old cache limit code because that seemed most > sensible for the use of the caches for regular catalog objects, but > I don't think LOs will have the same characteristics with respect to > either number of objects or locality of access.
Are you talking about syscache.c? I added a syscache entry for pg_largeobject_metadata, not pg_largeobject which contains data chunks. The pg_largeobject_metadata is a smaller catalog than most of system catalogs, such as pg_class. Thanks, -- KaiGai Kohei <kai...@kaigai.gr.jp> -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
