head	1.8;
access;
symbols
	REL7_4_29:1.7
	REL8_0_25:1.7
	REL7_4_28:1.7
	REL8_0_24:1.7
	REL7_4_27:1.7
	REL8_0_23:1.7
	REL7_4_26:1.7
	REL8_0_22:1.7
	REL7_4_25:1.7
	REL8_0_21:1.7
	REL7_4_24:1.7
	REL8_0_20:1.7
	REL7_4_23:1.7
	REL8_0_19:1.7
	REL7_4_22:1.7
	REL8_0_18:1.7
	REL7_4_21:1.7
	REL8_0_17:1.7
	REL7_4_20:1.7
	REL8_0_16:1.7
	REL7_3_21:1.7
	REL7_4_19:1.7
	REL8_0_15:1.7
	REL7_3_20:1.7
	REL7_4_18:1.7
	REL8_0_14:1.7
	REL7_3_19:1.7
	REL7_4_17:1.7
	REL8_0_13:1.7
	REL8_0_12:1.7
	REL7_3_18:1.7
	REL7_4_16:1.7
	REL8_0_11:1.7
	REL8_0_10:1.7
	REL7_4_15:1.7
	REL7_3_17:1.7
	REL8_0_9:1.7
	REL7_4_14:1.7
	REL7_3_16:1.7
	REL7_3_15:1.7
	REL7_4_13:1.7
	REL8_0_8:1.7
	REL7_3_14:1.7
	REL7_4_12:1.7
	REL8_0_7:1.7
	REL7_3_13:1.7
	REL7_4_11:1.7
	REL8_0_6:1.7
	REL7_3_12:1.7
	REL7_4_10:1.7
	REL8_0_5:1.7
	REL7_3_11:1.7
	REL7_4_9:1.7
	REL8_0_4:1.7
	REL7_2_8:1.6
	REL7_3_10:1.7
	REL7_4_8:1.7
	REL8_0_3:1.7
	REL8_0_2:1.7
	REL7_2_7:1.6
	REL7_3_9:1.7
	REL7_4_7:1.7
	REL8_0_1:1.7
	REL8_0_STABLE:1.7.0.10
	REL8_0_0:1.7.0.8
	REL8_0_0RC5:1.7
	REL8_0_0RC4:1.7
	REL8_0_0RC3:1.7
	REL8_0_0RC2:1.7
	REL8_0_0RC1:1.7
	REL8_0_0BETA5:1.7
	REL8_0_0BETA4:1.7
	REL7_4_6:1.7
	REL7_3_8:1.7
	REL7_2_6:1.6
	REL8_0_0BETA3:1.7
	REL8_0_0BETA2:1.7
	REL7_2_5:1.6
	REL7_4_5:1.7
	REL7_3_7:1.7
	REL7_4_4:1.7
	REL8_0_0BETA1:1.7
	REL7_4_3:1.7
	REL7_4_2:1.7
	REL7_3_6:1.7
	REL7_4_1:1.7
	REL7_3_5:1.7
	REL7_4:1.7
	REL7_4_RC2:1.7
	REL7_4_STABLE:1.7.0.6
	REL7_4_RC1:1.7
	REL7_4_BETA5:1.7
	REL7_4_BETA4:1.7
	REL7_4_BETA3:1.7
	REL7_4_BETA2:1.7
	WIN32_DEV:1.7.0.4
	REL7_4_BETA1:1.7
	REL7_3_4:1.7
	REL7_3_2:1.7
	REL7_2_4:1.6
	REL7_3_STABLE:1.7.0.2
	REL7_2_3:1.6
	REL7_2_STABLE:1.6.0.2
	REL7_2:1.6
	REL7_2_RC2:1.5
	REL7_2_RC1:1.5;
locks; strict;
comment	@# @;


1.8
date	2005.06.22.22.56.27;	author tgl;	state dead;
branches;
next	1.7;

1.7
date	2002.07.03.14.38.19;	author momjian;	state Exp;
branches;
next	1.6;

1.6
date	2002.01.31.19.13.53;	author momjian;	state Exp;
branches;
next	1.5;

1.5
date	2002.01.18.04.38.46;	author momjian;	state Exp;
branches;
next	1.4;

1.4
date	2002.01.15.04.50.37;	author momjian;	state Exp;
branches;
next	1.3;

1.3
date	2002.01.15.04.05.24;	author momjian;	state Exp;
branches;
next	1.2;

1.2
date	2002.01.14.22.54.44;	author momjian;	state Exp;
branches;
next	1.1;

1.1
date	2002.01.14.17.45.43;	author momjian;	state Exp;
branches;
next	;


desc
@@


1.8
log
@Remove contrib modules that have been agreed to be obsolete.
(There are more that will be removed once they've been copied to
pgfoundry.org.)
@
text
@                                 pg_upgrade


PG_UPGRADE IS NOT AVAILABLE FOR UPGRADES FROM 7.2.X.

This is a version of pg_upgrade which will allow a 7.3 to 7.3 migration
if you need to perform an initdb.  It has been only lightly tested. 
Please report any problems to the PostgreSQL lists.

Read the manual page for more information.  To view it:

	nroff -man pg_upgrade.1 | more

Bruce Momjian

2002-07-03
@


1.7
log
@Disable pg_upgrade for 7.3.
@
text
@@


1.6
log
@Add mention of recovery using pg_upgrade.
@
text
@d3 6
a8 4
This is a version of pg_upgrade which will migrate a 7.1 database to
7.2, or allow a 7.2 to 7.2 migration if you need to perform an initdb. 
It has been only lightly tested.  Please report any problems to the
PostgreSQL lists.
d16 1
a16 1
2002-01-14
@


1.5
log
@Enable /contrib/pg_upgrade, mention little testing.
@
text
@d10 1
a10 1
	nroff -man pg_upgrade.1 | $PAGER
@


1.4
log
@More cleanups with ideas from Peter.
@
text
@d3 4
a6 2
This is a version of pg_upgrade which will migrate a 7.1 database to 7.2,
or allow a 7.2 to 7.2 migration if you need to perform an initdb.
@


1.3
log
@Add Peter's portability and option suggestions.
@
text
@a12 10

--

To migrate this to newer versions of PostgreSQL:  

	1)  Update the version numbers at the top of the file
	2)  Search for specific version mentions in the script and update
	    accordingly.
	3)  Add changes for next version.

@


1.2
log
@Update permissions?
@
text
@d1 1
d3 2
d6 1
d8 1
a8 1
PG_UPGRADE(1)     PostgreSQL Client Applications    PG_UPGRADE(1)
d10 1
d12 1
a12 2
NNAAMMEE
       pg_upgrade - upgrade tool
d14 1
a14 3
SSYYNNOOPPSSIISS
       Allows upgrading from a previous release without reloading
       data
d16 1
a16 117
DDEESSCCRRIIPPTTIIOONN
       ppgg__uuppggrraaddee is a utility  for  upgrading  from  a  previous
       PostgreSQL release without reloading all the data. Not all
       PostgreSQL releases  can  use  this  utility.   Check  the
       release notes for details about your version.

       ppgg__uuppggrraaddee  must  be  run in two stages.  In phase one you
       must run ppgg__uuppggrraaddee with your old database installation in
       place.   In phase two, ppgg__uuppggrraaddee must be run on a freshly
       iinniittddbb'ed current  install.   In  both  phases,  the  same
       ppgg__uuppggrraaddee  script  matching  the  newly installed version
       must be used.

UUppggrraaddiinngg PPoossttggrreeSSQQLL wwiitthh ppgg__uuppggrraaddee
       1) Back up your existing  data  directory,  preferably  by
       making a complete dump with ppgg__dduummppaallll..

       2)  Copy  the  program _p_g_s_q_l_/_c_o_n_t_r_i_b_/_p_g___u_p_g_r_a_d_e_/_p_g___u_p_g_r_a_d_e
       from the current PostgreSQL  distribution  somewhere  into
       your path.

       3)  Change your working directory to the pgsql main direc-
       tory, and type:

       $$ ppgg__uuppggrraaddee --11

       to collect information about the old database  needed  for
       the upgrade.

       4) Do:

       $$ mmaakkee iinnssttaallll

       to install the new binaries.

       5)  Do:

       $$ ccdd ppggssqqll//ccoonnttrriibb//ppgg__rreesseettxxlloogg
       $$ mmaakkee iinnssttaallll

       to  install  the  _p_g___r_e_s_e_t_x_l_o_g  utility which is needed by
       ppgg__uuppggrraaddee.

       6) Run initdb to create a new template1 database  contain-
       ing  the system tables for the new release.  Make sure you
       use settings similar to those used in your  previous  ver-
       sion.



14 Jan 2002               PG_UPGRADE(1)                         1





PG_UPGRADE(1)     PostgreSQL Client Applications    PG_UPGRADE(1)


       7)  Start  the new _p_o_s_t_m_a_s_t_e_r_.  (Note: it is critical that
       no users connect to the server until the upgrade  is  com-
       plete.  You may wish to start the postmaster without -i or
       alter pg_hba.conf temporarily.)

       8)  Change your working directory to the pgsql main direc-
       tory again, and type:

       $$ ppgg__uuppggrraaddee --22

       The  program will do some checking to make sure everything
       is properly configured, and will  then  recreate  all  the
       databases  and  tables you had, but with no data.  It will
       then physically move the data files containing  non-system
       tables and indexes into the proper subdirectories.

       9)   Restore  your old _p_g___h_b_a_._c_o_n_f if needed to allow user
       logins.


       10)   Carefully  examine  the  contents  of  the  upgraded
       databases.  If you detect problems, you'll need to recover
       by restoring from your full  ppgg__dduummppaallll  backup.  You  can
       delete  the _p_g___u_p_g_r_a_d_e___i_n_f_o_/ directory when you are satis-
       fied.

       The upgraded databases will be in  an  un-vacuumed  state.
       You  will  probably  want  to  run a _V_A_C_U_U_M _A_N_A_L_Y_Z_E before
       beginning production work.

SSEEEE AALLSSOO
       initdb(1), postmaster(1), pg_dump(1), pg_dumpall(1), vacu-
       umdb(1)
























14 Jan 2002               PG_UPGRADE(1)                         2
d18 4
@


1.1
log
@Add README file.
@
text
@d15 1
a15 1
       pg_upgrade is a utility  for  upgrading  from  a  previous
d17 1
a17 1
       PostgreSQL releases can be handled this  way.   Check  the
d20 5
a24 5
       pg_upgrade  must  be  run in two stages.  In phase one you
       must run pg_upgrade with your old database installation in
       place.   In phase two, pg_upgrade must be run on a freshly
       initdb'ed current  install.   In  both  phases,  the  same
       pg_upgrade  script  matching  the  newly installed version
d29 1
a29 1
       making a complete dump with pg_dumpall.
d55 1
a55 1
       pg_upgrade.
d79 1
a79 1
       tory, and type:
d95 7
a101 6
       by restoring from your full pg_dump backup. You can delete
       the _p_g___u_p_g_r_a_d_e___i_n_f_o_/ directory when you are satisfied.

       The  upgraded  databases  will be in an un-vacuumed state.
       You will probably want to  run  a  _V_A_C_U_U_M  _A_N_A_L_Y_Z_E  bbeeffoorree
       bbeeggiinnnniinngg pprroodduuccttiioonn wwoorrkk..
a105 1

@
