diff --git a/INSTALL b/INSTALL index 5ae66b8853..8815bafd78 100644 --- a/INSTALL +++ b/INSTALL @@ -27,6 +27,9 @@ Table of Contents Installation Operation 5. Release Notes + Release 6.5.1 + Migration to v6.5.1 + Detailed Change List Release 6.5 Migration to v6.5 Multi-Version Concurrency Control @@ -55,7 +58,7 @@ Chapter 1. Introduction Chapter 2. Ports - This manual describes version 6.5 of Postgres. The + This manual describes version 6.5.1 of Postgres. The Postgres developer community has compiled and tested Postgres on a number of platforms. Check the web site (http://www.postgresql.org/docs/admin/ports.htm) for @@ -147,7 +150,7 @@ Currently Supported Platforms Platforms listed for v6.3.x and v6.4.x should also - work with v6.5, but we did not receive explicit + work with v6.5.1, but we did not receive explicit confirmation of such at the time this list was compiled. @@ -183,7 +186,7 @@ Unsupported Platforms Chapter 3. Installation Complete installation instructions for Postgres - v6.5. + v6.5.1. Before installing Postgres, you may wish to visit www.postgresql.org (http://www.postgresql.org) for up @@ -282,10 +285,8 @@ Installation Procedure the remaining steps in the installation will happen in this account. 4. Ftp file - ftp://ftp.postgresql.org/pub/postgresql-v6.5.tar.- - gz - (ftp://ftp.postgresql.org/pub/postgresql-v6.5.tar- - .gz) from the Internet. Store it in your home + ftp://ftp.postgresql.org/pub/postgresql-v6.5.1.tar.gz + from the Internet. Store it in your home directory. 5. Some platforms use flex. If your system uses flex then make sure you have a good version. To check, @@ -330,8 +331,12 @@ Installation Procedure /usr/include/FlexLexer.h and will add a link /usr/bin/flex++ which points to flex. 6. If you are not upgrading an existing system then - skip to step 9. If you are upgrading an existing - system then back up your database. For alpha- and + skip to step 9. If you are upgrading from 6.5, you + do not need to dump/reload or initdb. Simply + compile the source code, stop the postmaster, do a + "make install", and restart the postmaster. + If you are upgrading from 6.4.* or earlier, + back up your database. For alpha- and beta-level releases, the database format is liable to change, often every few weeks, with no notice besides a quick comment in the HACKERS mailing @@ -351,7 +356,7 @@ Installation Procedure pull the most recent version of pg_dumpall from the new distribution: $ cd - $ gunzip -c postgresql-v6.5.tar.gz \ + $ gunzip -c postgresql-v6.5.1.tar.gz \ | tar xvf - src/bin/pg_dump/pg_dumpall $ chmod a+x src/bin/pg_dump/pg_dumpall $ src/bin/pg_dump/pg_dumpall > db.out @@ -445,7 +450,7 @@ Installation Procedure $ exit 10. Unzip and untar the new source file. Type $ cd /usr/src/pgsql - $ gunzip -c ~/postgresql-v6.5.tar.gz | tar xvf - + $ gunzip -c ~/postgresql-v6.5.1.tar.gz | tar xvf - 11. Configure the source code for your system. It is this step at which you can specify your actual installation path for the build process (see the @@ -685,7 +690,7 @@ Installation Procedure a. Start the postmaster daemon running in the background by typing $ cd - $ postmaster -i + $ nohup postmaster -i > pgserver.log 2>&1 & b. Create a database by typing $ createdb c. Connect to the new database: @@ -867,7 +872,7 @@ Installation Procedure # Also delete old database directory tree if it is not in # /usr/local/pgsql_6_5/data - $ rm ~/postgresql-v6.5.tar.gz + $ rm ~/postgresql-v6.5.1.tar.gz 27. You will probably want to print out the documentation. If you have a Postscript printer, or have your machine already set up to accept @@ -894,10 +899,10 @@ Installation Procedure send a mail message to pgsql-ports@postgresql.org (mailto:pgsql-ports@postgresql.org) telling us the following: - o The version of Postgres (v6.5, 6.4.2, beta - 981014, etc.). - o Your operating system (i.e. RedHat v5.1 Linux - v2.0.34). + o The version of Postgres (v6.5.1, 6.5, beta + 990318, etc.). + o Your operating system (i.e. RedHat v5.2 Linux + v2.0.36). o Your hardware (SPARC, i486, etc.). o Did you compile, install and run the regression tests cleanly? If not, what source code did you