|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.113 2008/01/23 20:21:37 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.114 2008/02/13 22:44:06 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="backup"> |
4 | 4 | <title>Backup and Restore</title> |
@@ -1909,13 +1909,6 @@ pg_dumpall -p 5432 | psql -d postgres -p 6543 |
1909 | 1909 | of downtime for an upgrade. |
1910 | 1910 | </para> |
1911 | 1911 |
|
1912 | | - <para> |
1913 | | - In practice you probably want to test your client |
1914 | | - applications on the new setup before switching over completely. |
1915 | | - This is another reason for setting up concurrent installations |
1916 | | - of old and new versions. |
1917 | | - </para> |
1918 | | - |
1919 | 1912 | <para> |
1920 | 1913 | If you cannot or do not want to run two servers in parallel, you can |
1921 | 1914 | do the backup step before installing the new version, bring down |
@@ -1955,5 +1948,68 @@ psql -f backup postgres |
1955 | 1948 | moving an installation like this will not work.) |
1956 | 1949 | </para> |
1957 | 1950 | </note> |
| 1951 | + |
| 1952 | + <para> |
| 1953 | + In practice you probably want to test your client applications on the |
| 1954 | + new version before switching over completely. This is another reason |
| 1955 | + for setting up concurrent installations of old and new versions. When |
| 1956 | + testing a <productname>PostgreSQL</> major upgrade, consider the |
| 1957 | + following categories of possible changes: |
| 1958 | + </para> |
| 1959 | + |
| 1960 | + <variablelist> |
| 1961 | + |
| 1962 | + <varlistentry> |
| 1963 | + <term>Administration</term> |
| 1964 | + <listitem> |
| 1965 | + <para> |
| 1966 | + The capabilities available for administrators to monitor and control |
| 1967 | + the server often change and improve in each major release. |
| 1968 | + </para> |
| 1969 | + </listitem> |
| 1970 | + </varlistentry> |
| 1971 | + |
| 1972 | + <varlistentry> |
| 1973 | + <term>SQL</term> |
| 1974 | + <listitem> |
| 1975 | + <para> |
| 1976 | + Typically this includes new SQL command capabilities and not changes |
| 1977 | + in behavior, unless specifically mentioned in the release notes. |
| 1978 | + </para> |
| 1979 | + </listitem> |
| 1980 | + </varlistentry> |
| 1981 | + |
| 1982 | + <varlistentry> |
| 1983 | + <term>Library API</term> |
| 1984 | + <listitem> |
| 1985 | + <para> |
| 1986 | + Typically libraries like <application>libpq</> only add new |
| 1987 | + functionality, again unless mentioned in the release notes. |
| 1988 | + </para> |
| 1989 | + </listitem> |
| 1990 | + </varlistentry> |
| 1991 | + |
| 1992 | + <varlistentry> |
| 1993 | + <term>System Catalogs</term> |
| 1994 | + <listitem> |
| 1995 | + <para> |
| 1996 | + System catalog changes usually only affect database management tools. |
| 1997 | + </para> |
| 1998 | + </listitem> |
| 1999 | + </varlistentry> |
| 2000 | + |
| 2001 | + <varlistentry> |
| 2002 | + <term>Server C-language API</term> |
| 2003 | + <listitem> |
| 2004 | + <para> |
| 2005 | + This involved changes in the backend function API, which is written |
| 2006 | + in the C programming language. Such changes effect code that |
| 2007 | + references backend functions deep inside the server. |
| 2008 | + </para> |
| 2009 | + </listitem> |
| 2010 | + </varlistentry> |
| 2011 | + |
| 2012 | + </variablelist> |
| 2013 | + |
1958 | 2014 | </sect1> |
1959 | 2015 | </chapter> |