Re: PostgreSQL Limits and lack of documentation about them.
От | Peter Eisentraut |
---|---|
Тема | Re: PostgreSQL Limits and lack of documentation about them. |
Дата | |
Msg-id | 23360f8f-2ddb-53f4-e756-2f380ac33b31@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: PostgreSQL Limits and lack of documentation about them. (David Rowley <david.rowley@2ndquadrant.com>) |
Ответы |
Re: PostgreSQL Limits and lack of documentation about them.
Re: PostgreSQL Limits and lack of documentation about them. |
Список | pgsql-hackers |
That last sentence about the dropped columns is confusing to me: + <para> + Columns which have been dropped from the table also contribute to the + maximum column limit, although the dropped column values for newly + created tuples are internally marked as NULL in the tuple's null bitmap, + which does occupy space. + </para> So the dropped columns matter, but they are null, but the nulls matter too. What are we really trying to say here? Maybe this: Columns which have been dropped from the table also contribute to the maximum column limit. Moreover, although the dropped column values for newly created tuples are internally marked as NULL in the tuple's null bitmap, the null bitmap also occupies space. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: