On Wed, 16 Sep 2009, Tom Lane wrote:
* Shrink a table in place - when no space available
To be addressed by the UPDATE-style tuple-mover (which could be thought
of as VACUUM FULL rewritten to not use any special mechanisms).
Is there any synergy here with the needs of a future in-place upgrade
upgrade mechanism that handles page header expansion? That problem seemed
to always get stuck on the issue of how to move tuples around when the
pages were full. Not trying to drag the scope of this job out, just
looking for common ground that might be considered when designing the
tuple-mover if it could serve both purposes.
--
* Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
