Fwd: [GENERAL] 4B row limit for CLOB tables - Mailing list pgsql-hackers

From Roger Pack
Subject Fwd: [GENERAL] 4B row limit for CLOB tables
Date
Msg-id CAL1QdWc0Qo_J_zf5ZzBnLPhwZ7C_YwgxGZ0fKhN_TEc+z=fmqQ@mail.gmail.com
Whole thread Raw
Responses Re: Fwd: [GENERAL] 4B row limit for CLOB tables
List pgsql-hackers
>> On 1/29/15, Roger Pack <rogerdpack2@gmail.com> wrote:
>>> Hello.  I see on this page a mention of basically a 4B row limit for
>>> tables that have BLOB's
>>
>> Oops I meant for BYTEA or TEXT columns, but it's possible the
>> reasoning is the same...
>
> It only applies to large objects, not bytea or text.

OK I think I figured out possibly why the wiki says this.  I guess
BYTEA entries > 2KB will be autostored via TOAST, which uses an OID in
its backend.  So BYTEA has a same limitation.  It appears that
disabling TOAST is not an option [1].
So I guess if the number of BYTEA entries (in the sum all tables?
partitioning doesn't help?) with size > 2KB is > 4 billion then there
is actually no option there?  If this occurred it might cause "all
sorts of things to break"? [2]
Thanks!
-roger-

[1] http://www.postgresql.org/message-id/20130405140348.GC4326@awork2.anarazel.de
[2] http://www.postgresql.org/message-id/CAL1QdWfb-p5kE9DT2pMqBxohaKG=vxmDREmSBjc+7TkbOeKBBw@mail.gmail.com



pgsql-hackers by date:

Previous
From: David G Johnston
Date:
Subject: Re: tablespaces inside $PGDATA considered harmful
Next
From: Robert Haas
Date:
Subject: Re: Safe memory allocation functions