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?
Date: Fri, 03 Nov 2023 12:42:47 -0400
Message-ID: <3311709.1699029767@sss.pgh.pa.us> (raw)
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>
"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.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, daniel.westermann@dbi-services.com, pgsql-docs@lists.postgresql.org
Subject: Re: Incorrect mention of number of columns?
In-Reply-To: <3311709.1699029767@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox