Update with release notes for v6.5.1.

Change references from v6.5 to v6.5.1 in the installation instructions.
This commit is contained in:
Thomas G. Lockhart 1999-07-14 23:38:26 +00:00
parent c4747c7866
commit 98237b8e20
2 changed files with 62 additions and 22 deletions

45
HISTORY
View File

@ -5,6 +5,9 @@ by The PostgreSQL Development Team
PostgreSQL is Copyright © 1996-9 by the Postgres Global Development Group.
Table of Contents
Release 6.5.1
Migration to v6.5.1
Detailed Change List
Release 6.5
Migration to v6.5
Multi-Version Concurrency Control
@ -58,6 +61,43 @@ Table of Contents
Detailed Change List
Postgres95 Beta 0.01
Release 6.5.1
This is basically a cleanup release for 6.5. We have fixed a
variety of problems reported by 6.5 users.
Migration to v6.5.1
A dump/restore is not required for those running 6.5.
Detailed Change List
Fix for datetime constant problem on some platforms(Thomas)
Add NT README file
Portability fixes for linux_ppc, Irix, linux_alpha, OpenBSD, alpha
Remove QUERY_LIMIT, use SELECT...LIMIT
Fix for EXPLAIN on inheritance(Tom)
Patch to allow vacuum on multi-segment tables(Hiroshi)
R-Tree optimizer selectivity fix(Tom)
ACL file descriptor leak fix(Atsushi Ogawa)
New expresssion subtree code(Tom)
Avoid disk writes for read-only transactions(Vadim)
Fix for removal of temp tables if last transaction was aborted(Bruce)
Fix to prevent too large tuple from being created(Bruce)
plpgsql fixes
Allow port numbers 32k - 64k(Bruce)
Add ^ precedence(Bruce)
Rename sort files called pg_temp to pg_sorttemp(Bruce)
Fix for microseconds in time values(Tom)
Tutorial source cleanup
New linux_m68k port
Fix for sorting of NULL's in some cases(Tom)
Shared library dependencies fixed (Tom)
Fixed glitches affecting GROUP BY in subselects(Tom)
Fix some compiler warnings (Tomoaki Nishiyama)
Add Win1250 (Czech) support (Pavel Behal)
Release 6.5
This release marks a major step in the development team's mastery
@ -167,8 +207,6 @@ Migration to v6.5
Detailed Change List
Bug Fixes
---------
Fix text<->float8 and text<->float4 conversion functions(Thomas)
@ -350,9 +388,6 @@ Detailed Change List
leak(Tom)
New install commands for plpgsql(Jan)
Release 6.4.2
The 6.4.1 release was improperly packaged. This also has one

39
INSTALL
View File

@ -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