summaryrefslogtreecommitdiff
path: root/databases/postgresql/files
diff options
context:
space:
mode:
authorjlam <jlam>1999-09-19 04:24:53 +0000
committerjlam <jlam>1999-09-19 04:24:53 +0000
commit437b89763802f5c6c9ce2eec03c5465853edd9a2 (patch)
tree3bc7ee4f12f2669b0b065e52c4579738b645412b /databases/postgresql/files
parent2d82967cfceb8989a49efca8c41b42f49e66d9d1 (diff)
downloadpkgsrc-437b89763802f5c6c9ce2eec03c5465853edd9a2.tar.gz
Update postgresql to 6.5.1. Completely libtoolized and ldconfig statements
removed, but this should still function correctly on a.out systems. This package was originally submitted by D'Arcy J.M. Cain, but with major overhauling by me. Closes PR#7865 and relevant part of PR#8299. Major changes from version 6.4.2: Multi-version concurrency control(MVCC) This removes our old table-level locking, and replaces it with a locking system that is superior to most commercial database systems. In a traditional system, each row that is modified is locked until committed, preventing reads by other users. MVCC uses the natural multi-version nature of PostgreSQL to allow readers to continue reading consistent data during writer activity. Writers continue to use the compact pg_log transaction system. This is all performed without having to allocate a lock for every row like traditional database systems. So, basically, we no longer are restricted by simple table-level locking; we have something better than row-level locking. Hot backups from pg_dump pg_dump takes advantage of the new MVCC features to give a consistant database dump/backup while the database stays online and available for queries. Numeric data type We now have a true numeric data type, with user-specified precision. Temporary tables Temporary tables are guaranteed to have unique names within a database session, and are destroyed on session exit. New SQL features We now have CASE, INTERSECT, and EXCEPT statement support. We have new LIMIT/OFFSET, SET TRANSACTION ISOLATION LEVEL, SELECT ... FOR UPDATE, and an improved LOCK TABLE command. Speedups We continue to speed up PostgreSQL, thanks to the variety of talents within our team. We have sped up memory allocation, optimization, table joins, and row transfer routines. Ports We continue to expand our port list, this time including WinNT/ix86 and NetBSD/arm32. Interfaces Most interfaces have new versions, and existing functionality has been improved. Documentation New and updated material is present throughout the documentation. New FAQs have been contributed for SGI and AIX platforms. The Tutorial has introductory information on SQL from Stefan Simkovics. For the User's Guide, there are reference pages covering the postmaster and more utility programs, and a new appendix contains details on date/time behavior. The Administrator's Guide has a new chapter on troubleshooting from Tom Lane. And the Programmer's Guide has a description of query processing, also from Stefan, and details on obtaining the Postgres source tree via anonymous CVS and CVSup.
Diffstat (limited to 'databases/postgresql/files')
-rw-r--r--databases/postgresql/files/Makefile.custom23
-rw-r--r--databases/postgresql/files/md54
-rw-r--r--databases/postgresql/files/patch-sum22
-rw-r--r--databases/postgresql/files/pgsql.sh.tmpl26
-rw-r--r--databases/postgresql/files/post-install-notes4
5 files changed, 47 insertions, 32 deletions
diff --git a/databases/postgresql/files/Makefile.custom b/databases/postgresql/files/Makefile.custom
new file mode 100644
index 00000000000..df9990a3aa8
--- /dev/null
+++ b/databases/postgresql/files/Makefile.custom
@@ -0,0 +1,23 @@
+# GNU Makefile to libtoolize PostgreSQL build.
+#
+# This file is included by Makefile.global, which is included by every
+# sub-Makefile in the build tree. Makefiles for shared libraries include
+# Makefile.global then Makefile.shlib.
+#
+# $NetBSD: Makefile.custom,v 1.1 1999/09/19 04:24:54 jlam Exp $
+
+CUSTOM_INSTALL= ${LIBTOOL} ${INSTALL}
+CUSTOM_CC= ${LIBTOOL} ${CC}
+CUSTOM_CXX= ${LIBTOOL} ${CXX}
+
+# installation directory for documentation
+PGDOCS= ${POSTGRESDIR}/../share/doc/postgresql
+
+# Rules to build object files from source files.
+# ${LIBTOOL} requires that there not be a -o flag when in compile mode.
+#
+%.o: %.c
+ ${CC} ${CPPFLAGS} ${CFLAGS} -c $<
+
+%.o: %.cc
+ ${CXX} ${CPPFLAGS} ${CXXFLAGS} -c $<
diff --git a/databases/postgresql/files/md5 b/databases/postgresql/files/md5
index 8f7850213bf..969615f38e0 100644
--- a/databases/postgresql/files/md5
+++ b/databases/postgresql/files/md5
@@ -1,3 +1,3 @@
-$NetBSD: md5,v 1.4 1999/01/04 13:05:01 frueauf Exp $
+$NetBSD: md5,v 1.5 1999/09/19 04:24:54 jlam Exp $
-MD5 (postgresql-6.4.2.tar.gz) = 4f5e0409921892ca08fff2d8c099b3d7
+MD5 (postgresql-6.5.1.tar.gz) = f32379223026bd123552459958054d51
diff --git a/databases/postgresql/files/patch-sum b/databases/postgresql/files/patch-sum
index 2549c747f99..bba739f323d 100644
--- a/databases/postgresql/files/patch-sum
+++ b/databases/postgresql/files/patch-sum
@@ -1,9 +1,15 @@
-$NetBSD: patch-sum,v 1.3 1999/09/06 17:22:22 hubertf Exp $
+$NetBSD: patch-sum,v 1.4 1999/09/19 04:24:54 jlam Exp $
-MD5 (patch-aa) = 1d70af90ce5d83575005c26a5b2ec04c
-MD5 (patch-ab) = bd14b65459c105bf7c3c90117ba0f9e2
-MD5 (patch-ac) = 435ba13b38ab12e79c8fcb80d91da669
-MD5 (patch-ad) = c40ca1bdfd5fc3e78b78b989021ccb89
-MD5 (patch-ae) = 4128395164f2bd50fb06b14252b36720
-MD5 (patch-af) = c292166fbd98522459d388082329fb72
-MD5 (patch-ag) = 314afa41b6fa073f6215f5dab6978074
+MD5 (patch-aa) = 5e8179c837c09090840c1b56d5c396d8
+MD5 (patch-ab) = 75e575fb9211ed9357e3e4789452d055
+MD5 (patch-ac) = ef8e86f21029d7bab85f74d0bcec874c
+MD5 (patch-ad) = 0c7ad509908b626485eb152ce4ff4ba8
+MD5 (patch-ae) = 74a20ce1af43193ee2a0152e88d8c852
+MD5 (patch-af) = 055fe149d55089efa39eaaedafc611b6
+MD5 (patch-ag) = 9fe78b65dbd36b7c1f5d2a928639ad23
+MD5 (patch-ah) = cb80c672fa0b4e68802dafada7924030
+MD5 (patch-ai) = 27e8d614ef112a233c29debd6d6f4692
+MD5 (patch-aj) = c87c762e2732893073917e5af535cc52
+MD5 (patch-ak) = 1e22bf0d5770426882fef94d528f324e
+MD5 (patch-al) = 1394c41ef6b8d6e89bd4875606d6f8b5
+MD5 (patch-am) = 03f21739e54e2b7eca7094a5a61d97a1
diff --git a/databases/postgresql/files/pgsql.sh.tmpl b/databases/postgresql/files/pgsql.sh.tmpl
index 74b18e9a493..d0f26122a21 100644
--- a/databases/postgresql/files/pgsql.sh.tmpl
+++ b/databases/postgresql/files/pgsql.sh.tmpl
@@ -1,26 +1,12 @@
#!/bin/sh
-# $NetBSD: pgsql.sh.tmpl,v 1.3 1999/01/04 14:10:16 frueauf Exp $
+# $NetBSD: pgsql.sh.tmpl,v 1.4 1999/09/19 04:24:54 jlam Exp $
# FreeBSD Id: pgsql.sh.tmpl,v 1.3 1997/10/05 21:00:49 andreas Exp
-# pgsql.sh - postgresql startup file for FreeBSD and possibly *BSD (untested)
+# pgsql.sh - postgresql startup file for NetBSD
-# Changes:
-# - renamed startup script to be in sync with INSTALL file
-# - merged ldconfig start sequence from former postgrsql.sh script (andreas)
-# - modified the postmaster startup sequence as suggested in the
-# INSTALL file which was given as example for FreeBSD 2.2 (andreas)
-# - removed the commandline option
-# -D!!PREFIX!!/!!PGUSER!!/data \
-# because the postmaster process, which starts up under the
-# environment of the pgsql user, sets this with the PGDATA
-# environment variable in !!PREFIX!!/!!PGUSER!!/.profile
-#
-
-[ -d !!PREFIX!!/!!PGUSER!!/lib ] && /sbin/ldconfig -m !!PREFIX!!/!!PGUSER!!/lib
-
-[ -x !!PREFIX!!/pgsql/bin/postmaster ] && {
- su -l pgsql -c 'exec !!PREFIX!!/!!PGUSER!!/bin/postmaster \
- -S -o -F > !!PREFIX!!/!!PGUSER!!/errlog'
+if [ -x @PGPREFIX@/bin/postmaster ]; then
echo -n ' pgsql'
-}
+ su -l @PGUSER@ -c 'exec @PGPREFIX@/bin/postmaster \
+ -S -o -F > @PGPREFIX@/errlog'
+fi
diff --git a/databases/postgresql/files/post-install-notes b/databases/postgresql/files/post-install-notes
index 15d36a77b2b..aded8a71e2c 100644
--- a/databases/postgresql/files/post-install-notes
+++ b/databases/postgresql/files/post-install-notes
@@ -1,4 +1,4 @@
-$NetBSD: post-install-notes,v 1.2 1998/08/07 10:40:19 agc Exp $
+$NetBSD: post-install-notes,v 1.3 1999/09/19 04:24:54 jlam Exp $
Now that PostgreSQL is installed, you should read the documentation and
implementation guides. These can be found at:
@@ -9,6 +9,6 @@ You may wish to subscribe to the PostgreSQL user-support mailing list.
Send an e-mail to pgsql-questions-request@postgresql.org with the
text "subscribe" in the message body.
-If you build PostgreSQL with TCL support, then you can use the
+If you built PostgreSQL with TCL support, then you can use the
TCL/TK based database frontend "pgaccess" for database operations.