Le 6 juin 09 à 20:45, Josh Berkus a écrit :
So, here's what we need for 8.3 --> 8.4 for contrib modules:
That does nothing for external modules whose code isn't in PostgreSQL control. I'm thinking of those examples I cited up-thread --- and some more. (ip4r, temporal, prefix, hstore-new, oracfe, etc).
Could pg_migrator detect usage of "objects" oids (data types in relation, index opclass, ...) that are unknown to be in the standard - core + contrib distribution, and quit trying to upgrade the cluster in this case, telling the user his database is not supported?
Note that we expect NOT to have this issue for 8.4-->8.5, since we'll have a full module infrastructure by then. Really!
Note: added in-place upgrade to requirements of the first version of the feature.
-- dim -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
