Context Navigation

Changes between Initial Version and Version 2 of Ticket #3716

initial	v2
1		etry column).
2		The size was not shrinked during autovacuum, only full vacuum was able to
3		free the disk space.
	1	If you create a GiST index on a geometry(Polygon,4267) column and do updates on the table, the index size grows enormously even if the indexed column contains only nulls. This is a big problem that caused index to grow to tens of gigabytes for a table with just about 10000 rows, where indexed column contained only nulls, but was updated on a minutely basis (but not on the geometry column). The size was not shrinked during autovacuum, only full vacuum was able to free the disk space.
4	2
5	3	This is reproducable using following example that inserts 10000 rows and