From: | Roger Pack <rogerdpack2(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Fwd: [GENERAL] 4B row limit for CLOB tables |
Date: | 2015-01-30 17:54:42 |
Message-ID: | CAL1QdWc0Qo_J_zf5ZzBnLPhwZ7C_YwgxGZ0fKhN_TEc+z=fmqQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
>> On 1/29/15, Roger Pack <rogerdpack2(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Boyle | 2015-01-30 19:42:09 | Re: trouble adding a node to BDR |
Previous Message | Bill Moran | 2015-01-30 17:22:26 | Re: Catalog Bloat |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-01-30 17:58:36 | Re: Safe memory allocation functions |
Previous Message | David G Johnston | 2015-01-30 17:35:52 | Re: tablespaces inside $PGDATA considered harmful |