From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Lee Hachadoorian <lee(dot)hachadoorian(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Large Rows |
Date: | 2011-10-26 08:08:58 |
Message-ID: | CA+U5nM+dkDYjS3P4Fmu2tEZ=2_Tq1mUJoCw83YhmSCC33sKGUA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Oct 26, 2011 at 3:17 AM, Lee Hachadoorian
<lee(dot)hachadoorian(at)gmail(dot)com> wrote:
> I decided
> to try to combine all the sequences into one table using array columns.
> (This would actually make querying easier since the users wouldn't have to
> constantly JOIN the sequences in their queries.) Next problem: I run into
> the 8k row size limit once about half the columns are populated. As far as I
> can understand, even though a row theoretically supports a 1.6TB (!) row
> size, this only works for TOASTable data types (primarily text?). The vast
> majority of the 23k columns I'm storing are bigint.
Arrays are toastable, so you are getting an error from another source.
create table array_example as
select array_fill(1010110101010101, ARRAY[100000], ARRAY[1])::bigint[]
as arraycol;
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Daniele Varrazzo | 2011-10-26 08:42:13 | Re: missing chunk 0 for toast value ... |
Previous Message | Alexander Farber | 2011-10-26 08:08:56 | Re: Saving score of 3 players into a table |