RE: PostgreSQL Limits and lack of documentation about them.

From: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>
To: 'David Rowley' <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: RE: PostgreSQL Limits and lack of documentation about them.
Date: 2018-10-26 01:08:57
Message-ID: 0A3221C70F24FB45833433255569204D1FAE85A2@G01JPEXMBYT05
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

From: David Rowley [mailto:david(dot)rowley(at)2ndquadrant(dot)com]
> 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?

+1
As a user, I feel I would look for such information in appendix like "A Database limits" in Oracle's Database Reference manual:

https://docs.oracle.com/en/database/oracle/oracle-database/18/refrn/database-limits.html#GUID-ED26F826-DB40-433F-9C2C-8C63A46A3BFE

As a somewhat related topic, PostgreSQL doesn't mention the maximum values for numeric parameters. I was asked several times the questions like "what's the maximum value for max_connections?" and "how much memory can I use for work_mem?" I don't feel a strong need to specify those values, but I wonder if we should do something.

Regards
Takayuki Tsunakawa

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2018-10-26 02:26:36 Re: [HACKERS] Restricting maximum keep segments by repslots
Previous Message Michael Paquier 2018-10-26 00:31:48 Re: [PATCH] Tab complete EXECUTE FUNCTION for CREATE (EVENT) TRIGGER