Heikki Linnakangas wrote: > > For example CREATE/ALTER TABLE can cause problems. > > Yeah, if the pre-upgrade script determines the amount of reserved space > for each table, and sets it in pg_class or reloptions or whatever, it's > not clear how mwhat to do with tables created after the script is run. I > guess we need quick scan of pg_class before the actual upgrade to check > that you don't have newly-created tables, and refuse the upgrade if > there is.
This is where a pg_class column would be useful. You default the column value to -1. The pre-upgrade script sets the proper reserved space, and new tables get a -1 and you check for those just before the upgrade. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
