On Fri, Nov 3, 2023 at 05:04:46PM +0000, Daniel Westermann (DWE) wrote: > >"Daniel Westermann (DWE)" <daniel.westerm...@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 <br...@momjian.us> https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.