Zdenek Kotala wrote:
> Set general value for heap or btree is possible but not optimal. For
> example If you have 5TB table and page layout changes do not affected
> this table but some small table needs perform a cleanup then 5TB will be
> processed in general approach, but in optimal variant it will be mark as
> prepared on upgrade automatically.
Only the space reservation of *new* inserts/updates need to be
integrated in the backend. In addition to that, we'll need a pre-upgrade
script that decides which tables need processing, and process them. This
is no different whether we accept some generic space reservation patch
now, or backpatch a more precise one later.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
