From: | John Naylor <jcnaylor(at)gmail(dot)com> |
---|---|
To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PostgreSQL Limits and lack of documentation about them. |
Date: | 2018-11-06 11:00:51 |
Message-ID: | CAJVSVGWYpQ0n2ehUcpKeeLk4_CHNPJs+atctDgJ6tUGszztJ-A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/1/18, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> wrote:
> I've attached an updated patch, again it's just intended as an aid for
> discussions at this stage. Also included the rendered html.
Looks good so far. Based on experimentation with toasted columns, it
seems the largest row size is 452GB, but I haven't tried that on my
laptop. :-) As for the number-of-column limits, it's a matter of how
much detail we want to include. With all the numbers in my previous
email, that could probably use its own table if we include them all.
On 11/1/18, Nasby, Jim <nasbyj(at)amazon(dot)com> wrote:
> It’s a bit misleading to say “Can be increased by increasing BLKSZ and
> recompiling”, since you’d also need to re initdb. Given that messing with
> BLKSZ is pretty uncommon I would simply put a note somewhere that mentions
> that these values assume the default BLKSZ of 8192.
+1
-John Naylor
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2018-11-06 12:07:37 | Re: BUG #15449: file_fdw using program cause exit code error when using LIMIT |
Previous Message | Thomas Munro | 2018-11-06 10:50:33 | Re: BUG #15449: file_fdw using program cause exit code error when using LIMIT |