Re: Storing many big files in database- should I do it?

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Justin Graf <justin@magwerks.com>, David Wall <d.wall@computer.org>, Postgres General Postgres General <pgsql-general@postgresql.org>
Date: 2010-04-29T19:18:11Z
Lists: pgsql-general
Alvaro Herrera <alvherre@commandprompt.com> writes:
> 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.

However, that toast limit is per-table, whereas the pg_largeobject limit
is per-database.  So for example if you have a partitioned table then
the toast limit only applies per partition.  With large objects you'd
fall over at 4G objects (probably quite a bit less in practice) no
matter what.

			regards, tom lane