Re: PostgreSQL Limits and lack of documentation about them. - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: PostgreSQL Limits and lack of documentation about them.
Date
Msg-id 23360f8f-2ddb-53f4-e756-2f380ac33b31@2ndquadrant.com
Whole thread Raw
In response to Re: PostgreSQL Limits and lack of documentation about them.  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: PostgreSQL Limits and lack of documentation about them.  (Steve Crawford <scrawford@pinpointresearch.com>)
Re: PostgreSQL Limits and lack of documentation about them.  (David Rowley <david.rowley@2ndquadrant.com>)
List 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 by date:

Previous
From: Stephen Frost
Date:
Subject: Re: pg_stat_ssl additions
Next
From: Steve Crawford
Date:
Subject: Re: PostgreSQL Limits and lack of documentation about them.