Re: Incorrect mention of number of columns?
| От | Daniel Westermann (DWE) |
|---|---|
| Тема | Re: Incorrect mention of number of columns? |
| Дата | |
| Msg-id | GV0P278MB0419FF97A934DE5615F54DF3D2A5A@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM обсуждение исходный текст |
| Ответ на | Re: Incorrect mention of number of columns? (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Incorrect mention of number of columns?
|
| Список | pgsql-docs |
>"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.
>>> 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
В списке pgsql-docs по дате отправления: