Re: Storing many big files in database- should I do it? - Mailing list pgsql-general

From Tom Lane
Subject Re: Storing many big files in database- should I do it?
Date
Msg-id 17549.1272568691@sss.pgh.pa.us
Whole thread Raw
In response to Re: Storing many big files in database- should I do it?  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Storing many big files in database- should I do it?  (Justin Graf <justin@magwerks.com>)
List 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

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Storing many big files in database- should I do it?
Next
From: Greg Smith
Date:
Subject: Re: Performance and Clustering