Re: CLOB & BLOB limitations in PostgreSQL

From: Ivan Voras <ivoras(at)freebsd(dot)org>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: CLOB & BLOB limitations in PostgreSQL
Date: 2014-04-14 12:01:19
Message-ID: ligimg$non$1@ger.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On 11/04/2014 16:45, Jack.O'Sullivan(at)tessella(dot)com wrote:

> With point two, does this mean that any table with a bytea datatype is
> limited to 4 billion rows (which would seem in conflict with the
> "unlimited rows" shown by http://www.postgresql.org/about)? If we had
> rows where the bytea was a "null" entry would they contribute towards
> this total or is it 4 billion non-null entries?

This seems strange. A core developer should confirm this but it doesn't
make much sense - "bytea" fields are stored the same as "text" fields
(including varchar etc), i.e. the "varlena" internal representation, so
having the limit you are talking about would mean that any non-trivial
table with long-ish text fields would be limited to 2^32 entries...

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ivan Voras 2014-04-14 12:14:04 Re: encrypting data stored in PostgreSQL
Previous Message Rémi Cura 2014-04-14 09:58:08 Re: efficient way to do "fuzzy" join

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-04-14 12:46:59 Re: Patch: add psql tab completion for event triggers
Previous Message David Rowley 2014-04-14 11:19:40 Re: Window function optimisation, allow pushdowns of items matching PARTITION BY clauses