Re: [GENERAL] CLOB & BLOB limitations in PostgreSQL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Ivan Voras <ivoras(at)freebsd(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [GENERAL] CLOB & BLOB limitations in PostgreSQL
Date: 2014-04-15 01:45:33
Message-ID: 11465.1397526333@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Uh, I had not thought of this before but I think we need oids for toast
> storage, which would explain this wiki text:

> https://wiki.postgresql.org/wiki/BinaryFilesInDB

> Storing binary data using bytea or text data types

> Minus

> bytea and text data type both use TOAST
> limited to 1G per entry
> --> 4 Billion entries per table

> Is that correct?

No. It'd be 4 billion toasted-out-of-line entries per table (actually,
you'd start hitting performance issues well below that, but 4G would be
the hard limit). Small values, up to probably a KB or so, don't count
against the limit.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Augori 2014-04-15 02:17:20 Re: Unrecognized service
Previous Message David G Johnston 2014-04-15 01:31:14 Re: [GENERAL] CLOB & BLOB limitations in PostgreSQL

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-04-15 01:49:43 Re: assertion failure 9.3.4
Previous Message David G Johnston 2014-04-15 01:31:14 Re: [GENERAL] CLOB & BLOB limitations in PostgreSQL