Re: PostgreSQL Limits and lack of documentation about them. - Mailing list pgsql-hackers

From David Rowley
Subject Re: PostgreSQL Limits and lack of documentation about them.
Date
Msg-id CAKJS1f_4Jr2MuehkpZw5FnqVq0DWiCpq2icQ0wU11n9g5ZQXFw@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL Limits and lack of documentation about them.  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: PostgreSQL Limits and lack of documentation about them.  (John Naylor <jcnaylor@gmail.com>)
Re: PostgreSQL Limits and lack of documentation about them.  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On 8 November 2018 at 10:02, Robert Haas <robertmhaas@gmail.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

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: POC: Cleaning up orphaned files using undo logs
Next
From: Amit Langote
Date:
Subject: Re: move PartitionBoundInfo creation code