Re: Fwd: [GENERAL] 4B row limit for CLOB tables

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Álvaro Hernández <aht(at)8kdata(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fwd: [GENERAL] 4B row limit for CLOB tables
Date: 2015-04-24 13:23:17
Message-ID: 20150424132317.GW30322@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

* Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
> On Thu, Apr 23, 2015 at 11:24 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Having said all that, if we did try to fix it today, I'd imagine changing
> > TOAST value identifiers to int64 and inventing a new TOAST pointer format
> > for use when 32 bits isn't wide enough for the ID. But I think we're best
> > advised to hold off doing that until the need becomes pressing.
>
> Just out of curiosity, has anyone thought about inventing a new TOAST
> pointer format on the grounds that our TOAST pointers are unreasonably
> large?

I'd not thought about it, but sure sounds like a good idea from here.

Would be particularly great if we were able to do this and increase the
number of supported toast pointers and avoid having to go hunting for
unused identifiers due to wrapping.

Thanks!

Stephen

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Marc-André Goderre 2015-04-24 14:15:05 Re: Invalid memory alloc
Previous Message Vick Khera 2015-04-24 13:18:54 Re: COALESCE woes

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2015-04-24 13:38:34 Re: Moving ExecInsertIndexTuples and friends to new file
Previous Message Petr Jelinek 2015-04-24 13:09:55 Re: Replication identifiers, take 4