From: | John Naylor <jcnaylor(at)gmail(dot)com> |
---|---|
To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(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 07:02:24 |
Message-ID: | CAJVSVGW0nt0OMJ4O+VYHy4D8iLWjMVux8LfE1XW0_-P48Fsi6Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/8/18, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> wrote:
> On 8 November 2018 at 10:02, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> 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.
The language seems fine to me.
-John Naylor
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2018-11-08 07:15:43 | Re: Speeding up INSERTs and UPDATEs to partitioned tables |
Previous Message | Michael Paquier | 2018-11-08 07:00:26 | Re: Adding a TAP test checking data consistency on standby with minRecoveryPoint |