Update to PostgreSQL 8.0.postgresql-8_0_0-1

1 files changed, 114 insertions, 133 deletions

diff --git a/README.rpm-dist b/README.rpm-dist
index e230002..6a143e8 100644
--- a/README.rpm-dist
+++ b/README.rpm-dist
@@ -1,42 +1,44 @@
 README.rpm-dist
 -----------------------------------------------------------------------------
-Version 6.0, for the PostgreSQL 7.4-0.1PGDG RPMset.
+Version 8.0, for the PostgreSQL 8.0.0-1PGDG RPMset.
 Lamar Owen <lamar.owen@wgcr.org> 
 -----------------------------------------------------------------------------
 
 Contents:
- 0.)	Quick -i note.
+ 0.)	Quick note about '-i'
  1.)	Introduction, QuickStart, and credits
  2.)	PostgreSQL RPM packages and rationale
  3.)	Starting multiple postmasters
  4.)	Regression Testing
  5.)	Starting postmaster automatically on startup
- 6.)	Grand Unified Configuration(GUC) File.
- 7.)	Rebuilding the source RPM.
- 8.)	Contrib files.
- 9.)	Logging set up
+ 6.)	Grand Unified Configuration(GUC) File
+ 7.)	Logging set up
+ 8.)	Rebuilding from the source RPM
+ 9.)	Contrib files
 10.)	Further Information Resource
 
-QUICK '-i' NOTE
+QUICK NOTE ABOUT '-i'
 -----------------------------------------------------------------------------
 The postmaster '-i' option is NOT used by default in the initscript shipped
 with these RPMs.  Please do NOT modify the initscript to add the '-i' back
 in -- it will get overwritten on the next package upgrade.  Rather, see the
 section below on the Grand Unified Configuration file, which includes the
-recommended way to get '-i' functionality back.
+recommended way to get '-i' functionality.  Note that as of PostgreSQL 8.0,
+you don't need '-i' anyway if all you want to allow is local TCP/IP
+connections.
 
 INTRODUCTION
 -----------------------------------------------------------------------------
-This document exists to explain the layout of the RPM's for PostgreSQL,to 
+This document exists to explain the layout of the RPMs for PostgreSQL, to 
 describe various RPM specifics, and to document special features found
 in the RPMset.
 
-This document is written to be applicable to version 7.4 of PostgreSQL, 
-which is the current version of the RPM's as of this writing. More to the 
-point, versions prior to 7.3 are not documented here.
+This document is written to be applicable to version 8.0 of PostgreSQL, 
+which is the current version of the RPMs as of this writing. More to the 
+point, versions prior to 8.0 are not documented here.
 
-Official PostgreSQL Global Development Group RPM's have from version 7.1.2
-on carried a 'PGDG' after the release number.  Other RPMset's as distributed
+Official PostgreSQL Global Development Group RPMs have from version 7.1.2
+on carried a 'PGDG' after the release number.  Other RPMsets distributed
 with Linux distributions may have a different release number and initials.
 
 It is preferable for the distribution-specific set to be the one used, as
@@ -45,32 +47,25 @@ use them in preference.  If you want to stay up-to-date on the PostgreSQL
 core itself, use the PGDG generic set -- but understand that it is a 
 GENERIC set.
 
-These RPMs are designed to be LSB-compliant -- if you find this not to be the
-case, please let me know by way of the pgsql-ports@postgresql.org mailing
-list.
-
 These RPMs no longer support any sort of upgrading process other than that
 documented in the regular documentation.  That is, you must dump, upgrade,
-initdb, and restore your data.  The 7.2 to 7.3 migration can be quite
-difficult, even to the point of requiring hand-editing of the dumpfile.
+initdb, and restore your data.  Dump first, then remove the old server
+subpackage, install the new package, and restore the data from dump. (A new
+method of running multiple versions of PostgreSQL, along with the capability
+to run multiple postmasters, is in development, but was not ready for this
+release.)
 
-Thus, the 7.3 postgresql-server RPM specifically conflicted with prior
-versions.  The old server subpackage must be removed first, the new package
-installed, and the data restored from dump.  However, RPM itself did not
-honor this.  A new method of running multiple versions of PostgreSQL, along
-with the capability to run multiple postmasters, is in development, but was
-not ready for this release.
-
-A new section on running multiple postmasters has replaced the old upgrade
-instructions.
+SuSE has maintained their own RPMset for some time -- their documentation
+supercedes any found in this file.
 
 QUICKSTART
 -----------------------------------------------------------------------------
 For a fresh installation on a recent Red Hat or similar system, a simple
-service postgresql start
+	service postgresql start
 as root will prepare a new database (initdb), and start a postmaster that
-will listen on Unix socket 5432 only.  Edit /var/lib/pgsql/data/postgresql.conf
-to enable TCP/IP -- see the section on '-i.'
+will listen on localhost and Unix socket 5432 only.  Edit
+/var/lib/pgsql/data/postgresql.conf and pg_hba.conf if you want to allow
+remote access -- see the section on Grand Unified Configuration.
 
 The file /var/lib/pgsql/.bash_profile is now packaged to help with the 
 setting of environment variables. You may edit this file, and it won't be
@@ -80,12 +75,9 @@ to this file, so be sure to check .bash_profile.rpmnew after upgrading.
 The user 'postgres' is created during installation of the server subpackage.
 This user by default is UID and GID 26. The user has the default shell set to
 bash, and the home directory set to /var/lib/pgsql.  This user also has no
-default password -- in order to be able to su to from a non-root account
+default password -- in order to be able to su to it from a non-root account
 or login as 'postgres' you will need to set a password using passwd.
 
-While PygreSQL was split out from the main tarball, thanks to Kaj's work it
-is still included as the python subpackage.
-
 CREDITS
 -----------------------------------------------------------------------------
 Thomas Lockhart
@@ -107,62 +99,72 @@ Kaj J. Niemi
 
 POSTGRESQL RPM PACKAGES AND RATIONALE.
 -----------------------------------------------------------------------------
+PostgreSQL is split up into multiple packages so that users can 'pick and
+choose' what pieces are needed, and what dependencies are required.
+
 The RPMset is packaged in the following subpackages:
 
-postgresql:		Some clients and libraries, and documentation
+postgresql:		Key clients and libraries, and documentation
+postgresql-libs:	Client shared libraries
 postgresql-server:	Server executables and data files
-postgresql-devel:	Client-side development libraries
-postgresql-tcl:		TCL/TK client libraries and docs
+postgresql-devel:	Development libraries and include files
+postgresql-jdbc:	JARs for the JDBC client library
 postgresql-python:	The PygreSQL client library
-postgresql-jdbc:	JAR of the JDBC client
-postgresql-test:	The regression tests and associated files.
-postgresql-tcl:		Tcl client and PL ONLY.
-postgresql-libs:	client shared libraries.
-postgresql-docs:	extra documentation,such as the SGML doc sources.
-postgresql-contrib:	The contrib source tree, as well as selected binaries.
+postgresql-tcl:		Tcl client library (Pgtcl)
+postgresql-test:	The regression tests and associated files
+postgresql-docs:	Extra documentation, such as the tutorial files
+postgresql-contrib:	The contrib source tree, as well as selected binaries
 postgresql-pl:		PL/Perl (if possible on this dist), PL/Python, and PL/Tcl
 
+You have to install postgresql and postgresql-libs to do anything.
+postgresql-server is needed unless you only plan to use the clients to work
+with a remote PostgreSQL server. The others are optional.
+
 Note that there is no postgresql-perl, postgresql-odbc, postgresql-tk, or
 postgresql-plperl package any longer.  This is due to these portions being
-removed from the PostgreSQL source tarball.  The TK client package 'pgaccess'
-was the core of the -tk subpackage -- so the pgtksh client was rolled back
-into the -tcl package.
+removed from the PostgreSQL source tarball.
 
-PostgreSQL is split up into multiple packages so that users can 'pick and
-choose' what pieces are needed, and what dependencies are required.
+While PygreSQL was split out from the core PostgreSQL distribution, thanks to
+Kaj's work it is still included as the python subpackage.  Also, Pgtcl is
+still included as the tcl subpackage, although it is not part of the core
+distribution anymore.
 
 RPM FILE LOCATIONS.
 -----------------------------------------------------------------------------
-In compliance with the Linux FHS, the PostgreSQL RPM's install files in a manner
-not consistent with most of the PostgreSQL documentation.  According to the
-standard PostgreSQL documentation, PostgreSQL is installed under the directory
-/usr/local/pgsql, with executables, source, and data existing in various 
-subdirectories.
+To be in compliance with the Linux FHS, the PostgreSQL RPMs install files in
+a manner not consistent with most of the PostgreSQL documentation.  According
+to the standard PostgreSQL documentation, PostgreSQL is installed under the
+directory /usr/local/pgsql, with executables, source, and data existing in
+various subdirectories.
 
 Different distributions have different ideas of some of these file locations.
 In particular, the documentation directory can be /usr/doc, /usr/doc/packages,
 /usr/share/doc, /usr/share/doc/packages, or some other similar path.  The
-RedHat 7 locations are listed below. On SuSE <7.1, substitute 'postgres' for 
-'postgresql' below, and 'pg_tk' for 'postgresql-tk' below.
+Red Hat/Fedora locations are listed below. On SuSE <7.1, substitute 'postgres'
+for 'postgresql' below.
 
-However, the RPM's install the files like this:
+However, the RPMs install the files like this:
 Executables:		/usr/bin
-Libaries:		/usr/lib
+Libraries:		/usr/lib
 Documentation:		/usr/share/doc/postgresql-x.y.z
-Contrib:		/usr/share/doc/postgresql-x.y.z/contrib
+Contrib documentation:	/usr/share/doc/postgresql-contrib-x.y.z
 Source:			not installed
 Data:			/var/lib/pgsql/data
 Backup area:		/var/lib/pgsql/backup
 Templates:		/usr/share/pgsql
 Procedural Languages:	/usr/lib/pgsql
 Development Headers:	/usr/include/pgsql
+Localization data:	/usr/share/locale
 Other shared data:	/usr/share/pgsql
 Regression tests:	/usr/lib/pgsql/test/regress  (in the -test package)
-Documentation SGML:	/usr/share/doc/postgresql-docs-x.y.z
+Tutorial:		/usr/lib/pgsql/tutorial (in the -docs package)
+Extra documentation:	/usr/share/doc/postgresql-docs-x.y.z
 
-The above list references the Red Hat 7.x structure.  These locations may 
+On some 64-bit architectures, /usr/lib64 is used instead of /usr/lib.
+
+The above list describes the Red Hat/Fedora layout.  These locations may 
 change for other distributions.  Use of 'rpm -ql' for each package is
-recommended as the 'Official' location source.
+recommended as the 'official' information source.
 
 While it may seem gratuitous to place these files in different locations, the
 FHS requires it -- distributions should not ever touch /usr/local.  It may
@@ -170,8 +172,9 @@ also seem like more work to keep track of where everything is -- but, that's
 the beauty of RPM -- you don't have to keep track of the files, RPM does it
 for you.
 
-These RPM's are meant to be LSB-compliant.  If you find errors in them that
-cause thembe be non-compliant, please let me know.
+These RPMs are designed to be LSB-compliant -- if you find this not to be the
+case, please let me know by way of the pgsql-ports@postgresql.org mailing
+list.
 
 MULTIPLE POSTMASTERS
 -------------------------------------------------------------------------------
@@ -201,59 +204,46 @@ support experimental at this point in time.
 
 REGRESSION TESTING
 -------------------------------------------------------------------------------
-One of the features of the newer RPM sets is the capability to perform the 
+If you install the postgresql-test RPM then you can run the PostgreSQL
 regression tests.  These tests stress your database installation and produce
 results that give you assurances that the installation is complete, and that
 your database machine is up to the task.
 
 To run the regression tests under the RPM installation, make sure that
 postmaster has been started (if not, su to root and execute the
-'/etc/rc.d/init.d/postgresql start' init script), cd to
-/usr/lib/pgsql/test/regress, su to postgres, and execute the command line:
-time ./pg_regress.sh --schedule=parallel_schedule
-This command line will start the regression tests and will both show the
+"/etc/rc.d/init.d/postgresql start" init script), cd to
+/usr/lib/pgsql/test/regress, su to postgres, and execute "make check".
+This command will start the regression tests and will both show the
 results to the screen and store the results in the file regress.out.
-It will also give you a crude benchmark of how fast your machine performs.
-
-If tests fail, please see the file regression.diffs in that directory.  If
-you need help interpreting that file, contact the pgsql-ports list on
-postgresql.org.
-
-There are some tests that will almost always fail with RedHat Linux 5.x and 6.x
-installations.  The geometry, float8, and on occassion the random test will 
-fail.  These failures are normal for RedHat 5.2 and 6.1.  For RedHat 6.1 with
-certain i18n settings, there will be other tests fail.
 
-For 7.1RC1, all 76 tests passed on RedHat 6.2 and RedHat 7.0. This
-was accomplished by fiddling with the locale settings.  In version 7.1.2 this
-capability was removed -- you need to set your locale to 'C' before executing
-the first postmaster startup, or many more regression tests will fail.
+If any tests fail, see the file regression.diffs in that directory for details,
+and read the "Regression Tests" section of the PostgreSQL documentation to
+find out whether the differences are actually significant.  If you need help
+interpreting the results, contact the pgsql-ports list at postgresql.org.
 
-For interpretation of the regression tests, see the PostgreSQL documentation.
+After testing, say "make clean" to remove the files generated by the test
+script.
 
 STARTING POSTMASTER AUTOMATICALLY AT SYSTEM STARTUP
 -------------------------------------------------------------------------------
-RedHat Linux uses the System V Init package.  A startup script for PostgreSQL
+Red Hat Linux uses the System V Init package.  A startup script for PostgreSQL
 is provided in the server package, as /etc/rc.d/init.d/postgresql.  To start
 the postmaster, with sanity checking, as root, run
-service postgresql start
-to shut postmaster down,
-service postgresql stop
-There are other parameters to this script -- execute 'service postgresql' for a
-listing.
-
-To get this script to run at system startup or any time the system switches into
-runlevels 3, 4, or 5, run:
-chkconfig --add postgresql
-chkconfig --level 345 postgresql on
-and the proper symlinks will be created.  Check the chkconfig man page for more
+	service postgresql start
+To shut the postmaster down,
+	service postgresql stop
+There are other possible commands to this script -- execute
+'service postgresql' for a listing.
+
+To get this script to run at system startup or any time the system switches
+into runlevels 3, 4, or 5, run:
+	chkconfig --add postgresql
+	chkconfig --level 345 postgresql on
+and the proper symlinks will be created.  See the chkconfig man page for more
 information.  Note that this is manual -- while the startup script can include
 tags to allow chkconfig to automatically perform the symlinking, this is not
 done at this time.
 
-SuSE has maintained their own RPMset for some time -- their documentation
-supercedes any found in this file.
-
 GRAND UNIFIED CONFIGURATION (GUC) FILE
 -------------------------------------------------------------------------------
 The PostgreSQL server has many tunable parameters -- the file 
@@ -262,19 +252,22 @@ whole system.
 
 The RPM ships with the default file -- you will need to tune the
 parameters for your installation.  In particular, you might want to allow
-TCP/IP socket connections -- in order to allow these, you will need to edit
-the postgresql.conf file.  The line in question contains the string 
-'tcpip_socket' --want to both uncomment the line and set the parameter to true
-in order to get the TCP/IP socket to open.  
+nonlocal TCP/IP socket connections -- in order to allow these, you will need
+to edit the postgresql.conf file.  The line in question contains the string 
+'listen_addresses' -- you need to both uncomment the line and set the value
+to '*' to get the postmaster to accept nonlocal connections.  You'll also need
+to adjust pg_hba.conf appropriately.
 
-This is the same behavior the -i command line switch provides.  It is 
-preferable to use the postgresql.conf file, however, as future versions
-of the RPMset will allow multiple postmaster instances -- and that will only
-be possible thanks to the decoupling of settings out to each datadir.
+LOGGING SET UP
+-------------------------------------------------------------------------------
+By default, the postmaster's stderr log is directed into files placed in a
+pg_log subdirectory of the data directory (ie, /var/lib/pgsql/data/pg_log).
+The out-of-the-box configuration rotates among seven files, one for each
+day of the week.  You can adjust this by changing postgresql.conf settings.
 
 REBUILDING FROM SOURCE RPM
 -------------------------------------------------------------------------------
-If your distribution is not supported by the binary RPM's from PostgreSQL.org, 
+If your distribution is not supported by the binary RPMs from PostgreSQL.org, 
 you will need to rebuild from the source RPM.  Download the .src.rpm for this
 release.  You will need to be root to rebuild, unless you have already set up
 a non-root build environment.
@@ -291,7 +284,6 @@ build6x		undef	#don't build for Red Hat 6.x.  Define it to cause
 beta		0	#build with cassert and do not strip the binaries
 perl		1	#build the postgresql-perl package.
 tcl		1	#build the postgresql-tcl package.
-tkpkg		1	#build the postgresql-tk package.  
 jdbc		1	#build the postgresql-jdbc package.
 pls		1	#build the postgresql-pl package.
 test		1	#build the postgresql-test package.
@@ -302,13 +294,20 @@ ssl		1	#use OpenSSL support.
 kerberos	1	#use Kerberos 5 support.
 nls		1	#build with national language support.
 pam		1	#build with PAM support.
+runselftest	1	#do "make check" during the build.
 
 To use these defines, invoke a rebuild like this:
-rpm --rebuild --define 'perl 0' --define 'tcl 0' --define 'tkpkg 0'\
-	--define 'test 0' --define 'newintarray 1' --define 'kerberos 0' \
-	postgresql-7.1.3-1PGDG.src.rpm
-This line would disable the perl, tcl, tk, and test subpackages, enable the
-newer intarray code, and disable kerberos support.
+rpm --rebuild --define 'perl 0' --define 'tcl 0' \
+	--define 'test 0' --define 'runselftest 1' --define 'kerberos 0' \
+	postgresql-8.0.0-1PGDG.src.rpm
+This line would disable the perl, tcl, and test subpackages, enable the
+regression test run during build, and disable kerberos support.
+
+You might need to disable runselftest if there is an installed version of
+PostgreSQL that is a different major version from what you are trying to
+build.  The self test tends to pick up the installed libpq.so shared library
+in place of the one being built :-(, so if that isn't compatible the test will
+fail.  Also, you can't use runselftest when doing the build as root.
 
 More of these conditionals will be added in the future.
 
@@ -321,23 +320,6 @@ modules are in /usr/lib/pgsql for loadable modules, and binaries are in
 /usr/bin.  In the future these files may be split out, depending upon function
 and dependencies.
 
-LOGGING SET UP
--------------------------------------------------------------------------------
-To get rollable syslog set up, see the documentation for the file
-postgresql.conf, by default in the directory /var/lib/pgsql/data, as relates to
-the syslog options.  Then, add a line to /etc/syslog.conf, using the man page
-for syslog.conf as a source. Example:
-If postgresql.conf has the following lines for the syslog settings:
-syslog = 1 # range 0-2
-syslog_facility = 'LOCAL0'
-syslog_ident = 'postgres'
-
-Then you need to add the line to /etc/syslog.conf:
-local0.*			/var/log/postgresql 
-
-Then set up an entry in /etc/logrotate.d to roll postgresql the way you want it
-rolled.
-
 MORE INFORMATION
 -------------------------------------------------------------------------------
 You can get more information at http://www.postgresql.org
@@ -351,4 +333,3 @@ SuSE information is available at SuSE's website and information contacts.
 A 7.4 SuSE RPM is available on ftp.postgresql.org.  It is different from this
 RPM due to SuSE's different needs.
 -----------------------------------------------------------------------------
-