Justin Graf wrote: > On 4/29/2010 12:07 PM, David Wall wrote: > > > > > > Big downside for the DB is that all large objects appear to be stored > > together in pg_catalog.pg_largeobject, which seems axiomatically > > troubling that you know you have lots of big data, so you then store > > them together, and then worry about running out of 'loids'. > Huh ??? isn't that point of using bytea or text datatypes. > > I could have sworn bytea does not use large object interface it uses > TOAST or have i gone insane Each toasted object also requires an OID, so you cannot have more than 4 billion toasted attributes in a table. I've never seen this to be a problem in real life, but if you're talking about having that many large objects, then it will be a problem with toast too. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
