Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1qyxG3-00CJ0m-7I
	for pgsql-docs@arkaria.postgresql.org; Fri, 03 Nov 2023 16:42:55 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1qyxG1-001oOx-Qi
	for pgsql-docs@arkaria.postgresql.org; Fri, 03 Nov 2023 16:42:53 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1qyxG1-001oOo-JK
	for pgsql-docs@lists.postgresql.org; Fri, 03 Nov 2023 16:42:53 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1qyxFz-003n9m-8l
	for pgsql-docs@lists.postgresql.org; Fri, 03 Nov 2023 16:42:52 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 3A3GglGM3311710;
	Fri, 3 Nov 2023 12:42:47 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Daniel Westermann (DWE)" <daniel.westermann@dbi-services.com>
cc: "pgsql-docs@lists.postgresql.org" <pgsql-docs@lists.postgresql.org>
Subject: Re: Incorrect mention of number of columns?
In-reply-to: 
 <GV0P278MB0419E015B659F207254894FFD2A5A@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM>
References: 
 <GV0P278MB04193C52A42F4F860F34D707D2A5A@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM>
 <3308033.1699027957@sss.pgh.pa.us>
 <GV0P278MB0419E015B659F207254894FFD2A5A@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM>
Comments: In-reply-to "Daniel Westermann (DWE)"
 <daniel.westermann@dbi-services.com>
	message dated "Fri, 03 Nov 2023 16:18:45 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3311708.1699029767.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 03 Nov 2023 12:42:47 -0400
Message-ID: <3311709.1699029767@sss.pgh.pa.us>
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Archived-At: 
 <https://www.postgresql.org/message-id/3311709.1699029767%40sss.pgh.pa.us>
Precedence: bulk

"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 od=
d 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.

			regards, tom lane