On Wed, Feb 04, 2009 at 03:44:54PM -0500, Jason Dobies wrote: > > A lot of the primary keys are put into various tablespaces such as > [[2m_tbs]], [[4m_tbs]], [[64k_tbs]]. > > Is the intention that those tablespaces indicate roughly the size that > each key could occupy? Is it possible to use those as a guide when > converting from number to a postgres sized number column?
It's definitely not size of key. It is (intented to be used as) extent size, either first or next. So it roughly describes how big the object will be, and how fast it will change. You do not want index which is expected to occupy gigabytes to be allocated using 64kB blocks, and you do not want tiny lookup table which will always have three fixed records to occupy megabytes. -- Jan Pazdziora Satellite Engineering, Red Hat _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
