1- $PostgreSQL: pgsql/contrib/pg_upgrade/TESTING,v 1.2 2010/07/03 14:23:13 momjian Exp $
1+ $PostgreSQL: pgsql/contrib/pg_upgrade/TESTING,v 1.3 2010/07/09 16:51:23 momjian Exp $
22
33The most effective way to test pg_upgrade, aside from testing on user
44data, is by upgrading the PostgreSQL regression database.
@@ -22,11 +22,6 @@ Here are the steps needed to create a regression database dump file:
2222 a) Change CREATE FUNCTION shared object paths to use '$libdir'
2323 The old and new cluster will have different shared object paths.
2424
25- b) Remove 'regex_flavor' (not supported in Postgres 9.0)
26-
27- c) Change CREATE OR REPLACE LANGUAGE to CREATE LANGUAGE
28- The former syntax is only supported in Postgres 9.0.
29-
3025 d) Perform the load/dump twice
3126 This fixes problems with the ordering of COPY columns for
3227 inherited tables.
@@ -35,7 +30,11 @@ Here are the steps needed to create a regression database dump file:
3530 Commands like CREATE TRIGGER and ALTER TABLE sometimes have
3631 differences.
3732
38- f) Adjust extra_float_digits
33+ c) For pre-9.0, change CREATE OR REPLACE LANGUAGE to CREATE LANGUAGE
34+
35+ b) For pre-9.0, remove 'regex_flavor'
36+
37+ f) For pre-9.0, adjust extra_float_digits
3938Postgres 9.0 pg_dump uses extra_float_digits=-2 for pre-9.0
4039databases, and extra_float_digits=-3 for >= 9.0 databases.
4140It is necessary to modify 9.0 pg_dump to always use -3, and