Re: PostgreSQL Limits and lack of documentation about them.

From: Narayanan V <vnarayanan(dot)email(at)gmail(dot)com>
To: david(dot)rowley(at)2ndquadrant(dot)com
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: PostgreSQL Limits and lack of documentation about them.
Date: 2018-10-28 01:10:14
Message-ID: CAJP1NzMkyN99-BaD53v2446EQRrsWru9qfScxYz11fDwt9Lh7Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

+1 for inclusion in docs.

On Fri, Oct 26, 2018 at 4:00 AM David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
wrote:

> For a long time, we documented our table size, max columns, max column
> width limits, etc. in https://www.postgresql.org/about/ , but that
> information seems to have now been removed. The last version I can
> find with the information present is back in April this year. Here's a
> link to what we had:
>
> https://web.archive.org/web/20180413232613/https://www.postgresql.org/about/
>
> I think it's a bit strange that we don't have this information fairly
> early on in the official documentation. I only see a mention of the
> 1600 column limit in the create table docs. Nothing central and don't
> see mention of 32 TB table size limit.
>
> I don't have a patch, but I propose we include this information in the
> docs, perhaps on a new page in the preface part of the documents.
>
> Does anyone else have any thoughts about this?
>
> --
> David Rowley http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2018-10-28 02:27:11 Re: Comment fix and question about dshash.c
Previous Message Tomas Vondra 2018-10-27 23:01:49 Re: vacuum fails with "could not open statistics file" "Device or resource busy"