aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorPalle Girgensohn <girgen@FreeBSD.org>2007-01-09 16:29:35 +0000
committerPalle Girgensohn <girgen@FreeBSD.org>2007-01-09 16:29:35 +0000
commit6b11e898761ec7ced9bf9b652a24b78697eac863 (patch)
treeb375d70b112b334c43c9daa281851082f36a60da /UPDATING
parentb17127f51b50b9d89242d52a5b23d5c580fe5f75 (diff)
downloadports-6b11e898761ec7ced9bf9b652a24b78697eac863.tar.gz
ports-6b11e898761ec7ced9bf9b652a24b78697eac863.zip
Notes
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING13
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