Re: PostgreSQL Limits and lack of documentation about them.

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: John Naylor <jcnaylor(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL Limits and lack of documentation about them.
Date: 2018-11-08 03:13:49
Message-ID: CAKJS1f_4Jr2MuehkpZw5FnqVq0DWiCpq2icQ0wU11n9g5ZQXFw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8 November 2018 at 10:02, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> IMHO, documenting that you can get up to 1600 integer columns but only
> 1002 bigint columns doesn't really help anybody, because nobody has a
> table with only one type of column, and people usually want to have
> some latitude to run ALTER TABLE commands later.
>
> It might be useful for some users to explain that certain things will
> should work for values < X, may work for values between X and Y, and
> will definitely not work above Y. Or maybe we can provide a narrative
> explanation rather than just a table of numbers. Or both. But I
> think trying to provide a table of exact cutoffs is sort of like
> tilting at windmills.

I added something along those lines in a note below the table. Likely
there are better ways to format all this, but trying to detail out
what the content should be first.

Hopefully I I've addressed the other things mentioned too.

--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

Attachment Content-Type Size
dblimits.html text/html 5.4 KB
v3-0001-Add-documentation-section-appendix-detailing-some.patch application/octet-stream 5.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2018-11-08 03:59:27 Re: move PartitionBoundInfo creation code
Previous Message Thomas Munro 2018-11-08 03:02:39 Re: POC: Cleaning up orphaned files using undo logs