| From: | Roger Pack <rogerdpack2(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Álvaro Hernández Tortosa <aht(at)8kdata(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Fwd: [GENERAL] 4B row limit for CLOB tables |
| Date: | 2015-04-27 13:07:06 |
| Message-ID: | CAL1QdWfwDGPScY7uBnfVpjzbgb1xzvAHEGbVXRFhj-hZgi0ugQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 4/27/15, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> On 4/25/15 1:19 PM, Bruce Momjian wrote:
>> Note if you are storing a table with rows that exceed 2KB in size
>> (aggregate size of each row) then the "Maximum number of rows in a
>> table" may be limited to 4 Billion, see TOAST.
>
> That's not accurate though; you could be limited to far less than 4B
> rows. If each row has 10 fields that toast, you'd be limited to just
> 400M rows.
Good point. I noted that on the TOAST wiki page now, at least (and
also mentioned that using partitioning is a "work around" for now).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc-André Goderre | 2015-04-27 13:45:01 | Re: Invalid memory alloc |
| Previous Message | Evan Martin | 2015-04-27 12:45:25 | Workaround for bug #13148 (deferred EXCLUDE constraint violation) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-04-27 13:43:25 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
| Previous Message | Michael Paquier | 2015-04-27 12:50:58 | Re: collate.linux.utf8 test coverage |