Say hello to postgresql-8.0. Some of the highlights of the new version

are savepoints (within transactions), point-in-time recovery and
tablespaces. Check out the release notes and the shiny new
PostgreSQL.org website at:

http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0

The port uses the new postgresql ports' layout and is split into a
server and a client part. The following knobs can be used by ports
depending on PostgreSQL:

# USE_PGSQL     - Add PostgreSQL client dependency.
#                 If no version is given (by the maintainer via the port or
#                 by the user via defined variable), try to find the
#                 currently installed version.  Fall back to default if
#                 necessary (PostgreSQL-7.4 = 74).
# DEFAULT_PGSQL_VER
#               - PostgreSQL default version. Can be overridden within a port.
#                 Default: 74.
# WANT_PGSQL_VER
#               - Maintainer can set an arbitrary version of PostgreSQL by
#                 using it.
# BROKEN_WITH_PGSQL
#               - This variable can be defined if the ports doesn't support
#                 one or more versions of PostgreSQL.

PR:		75344
Approved by:	portmgr@ (kris), ade & sean (mentors)

1 files changed, 4 insertions, 26 deletions

diff --git a/databases/postgresql84-server/pkg-message-server b/databases/postgresql84-server/pkg-message-server
index 7957a3814c58..56e7442a2f42 100644
--- a/databases/postgresql84-server/pkg-message-server
+++ b/databases/postgresql84-server/pkg-message-server
@@ -1,36 +1,14 @@
-
-Specific for updating 7.4.1->7.4.x:
-
-   A dump/restore is *not* required for those running 7.4, BUT:
-
-   If you want to install the fixes in the information schema you will
-   need to reload it into the database. This is either accomplished by
-   initializing a new cluster by running "initdb", or by running the
-   following sequence of SQL commands in each database (ideally including
-   template1) as a superuser in psql, after installing the new release:
-
-DROP SCHEMA information_schema CASCADE;
-\i /usr/local/pgsql/share/information_schema.sql
-
-   Fixes to the information schema (from HISTORY):
-     * Fix information schema for bit data types (Peter)
-     * Fix information schema view constraint_column_usage for foreign
-       keys (Peter)
-
-=====================================================================
-
 For procedural languages and postgresql functions, please note that
-you might have to update them when updating the server. For example,
-the "elog" method disappeared in postgresql-7.4, so postgresql-contrib
-must be updated along with the server.
+you might have to update them when updating the server.
 
 If you have many tables and many clients running, consider raising
 kern.maxfiles using sysctl(8), or reconfigure your kernel
 appropriately.
 
 You should vacuum and backup your database regularly. There is a
-periodic script, /usr/local/etc/periodic/daily/502.pgsql, that you may
-find useful. See the script for instructions.
+periodic script, ${LOCALBASE}/etc/periodic/daily/502.pgsql, that you
+may find useful. Per default, it perfoms vacuum on all databases
+nightly. See the script for instructions.
 
 To allow many simultaneous connections to your PostgreSQL server, you
 should raise the SystemV shared memory limits in your kernel. Here are