Fixing problems with the recent security patch: When bison was not

installed, the patched gram.y file would not be used and the security
patch would be a no-op. Also, I've had reports of compilation errors
related to bison.

Since checking for the correct version of bison is hard and error
prone, I'm doing what the postgresql distribution does - patching the
yacc:ed .c file to get rid of the building dependency.

Bumping portrevision of -server.

Pointy hat to:	me
Noticed by:	Mike Harding and others
Security:	http://www.vuxml.org/freebsd/6b4b0b3f-8127-11d9-a9e7-0001020eed82.html
Approved by:	seanc (implicit)

1 files changed, 13 insertions, 0 deletions

diff --git a/UPDATING b/UPDATING
index d87b759092cc..ab1b19f7f3aa 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.
 
+20050511:
+  AFFECTS: users of databases/postgresql??-(server|contrib)
+  AUTHOR: girgen@FreeBSD.org
+
+  The PostgreSQL ports have been updated to latest versions. A
+  security problem in the template database requires a simple SQL
+  command to be run on each database. because these problems are
+  really incorrect system catalog entries. Updating to a new release
+  will NOT by itself solve the problems in an existing
+  installation.
+
+  See http://www.postgresql.org/about/news.315 for details.
+
 20050501:
   AFFECTS: users of lang/ocaml based applications and libraries
   AUTHOR: lioux@FreeBSD.org