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 $
2
2
3
3
The most effective way to test pg_upgrade, aside from testing on user
4
4
data, is by upgrading the PostgreSQL regression database.
@@ -22,11 +22,6 @@ Here are the steps needed to create a regression database dump file:
22
22
a) Change CREATE FUNCTION shared object paths to use '$libdir'
23
23
The old and new cluster will have different shared object paths.
24
24
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
-
30
25
d) Perform the load/dump twice
31
26
This fixes problems with the ordering of COPY columns for
32
27
inherited tables.
@@ -35,7 +30,11 @@ Here are the steps needed to create a regression database dump file:
35
30
Commands like CREATE TRIGGER and ALTER TABLE sometimes have
36
31
differences.
37
32
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
39
38
Postgres 9.0 pg_dump uses extra_float_digits=-2 for pre-9.0
40
39
databases, and extra_float_digits=-3 for >= 9.0 databases.
41
40
It is necessary to modify 9.0 pg_dump to always use -3, and
0 commit comments