On Tue, May 31, 2022 at 01:22:44PM -0400, Dave Cramer wrote: > > > On Tue, 31 May 2022 at 10:49, Tom Lane <t...@sss.pgh.pa.us> wrote: > > Dave Cramer <davecramer@postgres.rocks> writes: > > On Tue, 31 May 2022 at 10:16, Tom Lane <t...@sss.pgh.pa.us> wrote: > >> We've generally felt that the existing "columns per table" limit is > >> sufficient detail here. > > > ISTM that adding detail is free whereas the readers time to figure out > why > > and where this number came from is not. > > Detail is far from "free". Most readers are going to spend more time > wondering what the difference is between "columns per table" and "columns > per tuple", and which limit applies when, than they are going to save by > having the docs present them with two inconsistent numbers. > > > Sounds to me like we are discussing different sides of the same coin. On one > hand we have readers of the documentation who may be confused, > and on the other hand we have developers who run into this and have to spend > time digging into the code to figure out what's what.
How many people ask about this limit. I can't remember one. -- Bruce Momjian <br...@momjian.us> https://momjian.us EDB https://enterprisedb.com Indecision is a decision. Inaction is an action. Mark Batterson
