diff options
author | Bruce Momjian <bruce@momjian.us> | 2010-07-25 03:28:32 +0000 |
---|---|---|
committer | Bruce Momjian <bruce@momjian.us> | 2010-07-25 03:28:32 +0000 |
commit | f31b1fd7c1af812561f8729f80ecc8ad55f81a2a (patch) | |
tree | d628c7ec119e45e43bf6d58a7246b5a471f73528 /doc/src | |
parent | c3f903aca7e5f75d6deb0acc2c758791ad9bfdd4 (diff) | |
download | postgresql-f31b1fd7c1af812561f8729f80ecc8ad55f81a2a.tar.gz postgresql-f31b1fd7c1af812561f8729f80ecc8ad55f81a2a.zip |
Prevent pg_upgrade from migrating databases that use reg* data types
where the oid is not preserved by pg_upgrade (everything but pg_type).
Update documentation.
Per bug report from depstein@alliedtesting.com.
Diffstat (limited to 'doc/src')
-rw-r--r-- | doc/src/sgml/pgupgrade.sgml | 28 |
1 files changed, 21 insertions, 7 deletions
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml index 69ff9dba1b2..e7e858e1a71 100644 --- a/doc/src/sgml/pgupgrade.sgml +++ b/doc/src/sgml/pgupgrade.sgml @@ -1,4 +1,4 @@ -<!-- $PostgreSQL: pgsql/doc/src/sgml/pgupgrade.sgml,v 1.12 2010/05/25 15:55:28 momjian Exp $ --> +<!-- $PostgreSQL: pgsql/doc/src/sgml/pgupgrade.sgml,v 1.13 2010/07/25 03:28:32 momjian Exp $ --> <sect1 id="pgupgrade"> <title>pg_upgrade</title> @@ -445,9 +445,9 @@ psql --username postgres --file script.sql postgres </listitem> </orderedlist> - </sect2> + </sect2> - <sect2> + <sect2> <title>Limitations in migrating <emphasis>from</> PostgreSQL 8.3</title> <para> @@ -514,16 +514,30 @@ psql --username postgres --file script.sql postgres version 8.4 or later of the one-click distribution. It is not possible to upgrade from the MSI installer to the one-click installer. </para> + + </sect2> + + <sect2> + <title>Notes</title> + + <para> + <application>pg_upgrade</> does not support migration of databases + containing these reg* system oid-referencing data types: + <type>regproc</>, <type>regprocedure</>, <type>regoper</>, + <type>regoperator</>, <type>regclass</>, <type>regconfig</>, and + <type>regdictionary</>. (<type>regtype</> can be migrated.) + </para> <para> - All failure, rebuild, and reindex cases will be reported by <application>pg_upgrade</> - if they affect your installation; post-migration scripts to rebuild - tables and indexes will be automatically generated. + All failure, rebuild, and reindex cases will be reported by + <application>pg_upgrade</> if they affect your installation; + post-migration scripts to rebuild tables and indexes will be + generated automatically. </para> <para> For deployment testing, create a schema-only copy of the old cluster, - insert dummy data, and migrate that. + insert dummy data, and migrate that. </para> <para> |