| From: | "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Incorrect mention of number of columns? |
| Date: | 2023-11-03 17:04:46 |
| Message-ID: | GV0P278MB0419FF97A934DE5615F54DF3D2A5A@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
>"Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)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.
Regards
Daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-11-03 17:08:50 | Re: Incorrect mention of number of columns? |
| Previous Message | Bruce Momjian | 2023-11-03 16:53:46 | Re: Version 14/15 documentation Section "Alter Default Privileges" |