Date: Fri, 3 Nov 2023 13:08:50 -0400
From: Bruce Momjian <bruce@momjian.us>
To: "Daniel Westermann (DWE)" <daniel.westermann@dbi-services.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
	"pgsql-docs@lists.postgresql.org" <pgsql-docs@lists.postgresql.org>
Subject: Re: Incorrect mention of number of columns?
Message-ID: <ZUUpIt9f-31FVw0c@momjian.us>
References: 
 <GV0P278MB04193C52A42F4F860F34D707D2A5A@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM>
 <3308033.1699027957@sss.pgh.pa.us>
 <GV0P278MB0419E015B659F207254894FFD2A5A@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM>
 <3311709.1699029767@sss.pgh.pa.us>
 <GV0P278MB0419FF97A934DE5615F54DF3D2A5A@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <GV0P278MB0419FF97A934DE5615F54DF3D2A5A@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM>
Archived-At: 
 <https://www.postgresql.org/message-id/ZUUpIt9f-31FVw0c%40momjian.us>
Precedence: bulk

On Fri, Nov  3, 2023 at 05:04:46PM +0000, Daniel Westermann (DWE) wrote:
> >"Daniel Westermann (DWE)" <daniel.westermann@dbi-services.com> writes:
> >>> Yeah, but populating it would not (unless many of the columns were
> >>> NULL).
> 
> >> Ok, but then should the documentation be more precise? It seems a bit odd to
> let users create such a table without at least a warning.
> 
> >Given the impact of NULLs, and the fact that usually tables have some
> >variable-width columns, I doubt that a creation-time warning could be
> >accurate enough to be useful.
> 
> I am not speaking about a warning at creation time, but rather a warning in the
> docs. Something like: Although a table with e.g. 1600 bigint columns can be
> created, creating a tuple of more than 8160 bytes will fail.

It is in the "limits" docs:

	https://www.postgresql.org/docs/current/limits.html

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.