Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17.

Release notes:
http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17
http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15
http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10
http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6
http://www.postgresql.org/docs/8.2/static/release-8-2-1.html

The server-side utilities of postgresql (initdb, initlocation,
ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now
installed by the respective postgresql*-server port (previously they
where installed with the client). If you update the client, you should
also update the server to make sure you are not left without the
server-side tools. Do something like:

    portupgrade postgresql-client postgresql-server

1 files changed, 13 insertions, 0 deletions

diff --git a/UPDATING b/UPDATING
index 849229536b3e..9144bad6ce01 100644
--- a/UPDATING
+++ b/UPDATING
@@ -6,6 +6,19 @@ You should get into the habit of checking this file for changes each
 time you update your ports collection, before attempting any port
 upgrades.
 
+20070109:
+  AFFECTS: users of databases/postgresql*
+  AUTHOR: girgen@FreeBSD.org
+
+  The server-side utilities of postgresql (initdb, initlocation,
+  ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now
+  installed by the respective postgresql*-server port (previously
+  they where installed with the client). If you update the client, you
+  should also update the server to make sure you are not left without
+  the server-side tools. Do something like:
+
+    portupgrade postgresql-client postgresql-server
+
 20070105:
   AFFECTS: users of mail/spamprobe
   AUTHOR: stefan@FreeBSD.org