From: | Roger Pack <rogerdpack2(at)gmail(dot)com> |
---|---|
To: | Steve Atkins <steve(at)blighty(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: 4B row limit for CLOB tables |
Date: | 2015-01-29 21:58:14 |
Message-ID: | CAL1QdWe-JnsD9CBVUffUoaQrUDT8a3MHLJn+La5um=-mW==ULw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On 1/29/15, Steve Atkins <steve(at)blighty(dot)com> wrote:
>
> On Jan 29, 2015, at 9:53 AM, Roger Pack <rogerdpack2(at)gmail(dot)com> wrote:
>
>> 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 > 8KB will be autostored via TOAST, which uses an OID in
its backend. So BYTEA have the 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 > 8KB is > 4 billion then there
is actually no option there? (I'm not running into that case just
conjecturing).
Thanks!
-roger-
[1] http://www.postgresql.org/message-id/20130405140348.GC4326@awork2.anarazel.de
From | Date | Subject | |
---|---|---|---|
Next Message | Israel Brewster | 2015-01-29 22:12:26 | Server statistics monitoring? |
Previous Message | Adrian Klaver | 2015-01-29 21:14:27 | Re: Building extensions against OpenSCG RPM packages |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-01-29 21:59:46 | Re: jsonb, unicode escapes and escaped backslashes |
Previous Message | Andres Freund | 2015-01-29 21:48:15 | Re: jsonb, unicode escapes and escaped backslashes |