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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Justin Graf <justin(at)magwerks(dot)com>, David Wall <d(dot)wall(at)computer(dot)org>, Postgres General Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Storing many big files in database- should I do it?
Date: 2010-04-29 19:18:11
Message-ID: 17549.1272568691@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alvaro Herrera <alvherre(at)commandprompt(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Smith 2010-04-29 19:21:20 Re: Performance and Clustering
Previous Message Alvaro Herrera 2010-04-29 19:11:40 Re: Storing many big files in database- should I do it?