Bruce Momjian napsal(a):
Zdenek Kotala wrote:
Bruce Momjian napsal(a):
Zdenek Kotala wrote:
<snip>
1) Data does not fit on the new page. It will be solve by pre-upgrade check
which reserve space on each page, before upgrade.
Rather than specifying free space as an amount, I was thinking of having
a boolean like 'ready_for_upgrade' and the system internally would know
how much free space for each page and tuple.
You need booth, flag which shows you that the relation/database is ready for
upgrade and free space reservation configuration for each column. System cannot
know it because PostgreSQL is not oracle :-). It does not know what will happend
during next version development :-). It have to be setup by pre-upgrade script.
So every Postgres version will allow space reservation based on the
table and page, and the pre-upgrade script will set those values based
on the table's columns --- makes sense, and avoids the need for a minor
update to Postgres to add new code --- good idea.
yes, exactly.
Zdenek
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
