A ports freeze means that commits will be few and far between and only by approval.

Number of commits found: 22

Update PostgreSQL to latest version , 8.1.15

Update PostgreSQL to latest versions.

http://www.postgresql.org/docs/current/static/release-8-3-5.html
http://www.postgresql.org/docs/current/static/release-8-2-11.html
http://www.postgresql.org/docs/current/static/release-8-1-15.html
http://www.postgresql.org/docs/current/static/release-8-0-19.html
http://www.postgresql.org/docs/current/static/release-7-4-23.html

Note that the GiST problem mentioned does not apply to users of
the FreeBSD port, since the previous version of PostgreSQL never
reached the ports tree, due to the freeze of the tree pending the
FreeBSD 7.1 update.

PR:     121848, 124713

Update ICU patch to chase update of autoconf 2.61 -> 2.62

PR:             ports/126773
Submitted by:   Robert Schulze

Updates of the PostgreSQL ports

Updates for all maintained versions of PostgreSQL are available today:
8.3.3, 8.2.9, 8.1.13, 8.0.17 and 7.4.21.  These releases fix more than
two dozen minor issues reported and patched over the last few months.
All PostgreSQL users should plan to update at their earliest
convenience. People in affected time zones, in particular, should
upgrade as soon as possible.

Release Notes:
        http://www.postgresql.org/docs/8.3/static/release.html

Also, fix umask error in periodic script [1].

PR:             ports/124457 [1]
Submitted by:   Alexandre Perrin

Fix SIZE line for pg-8111-icu-xx-2008-02-19.diff.gz

Chase ICU version 3.8
HIER patch's web site has disappeared. Put the patches on freefall
until I can get hold of the author.

Fix bad ICU patch file

Update all PostgreSQL ports to latest versions.

This includes a bunch of security fixes: CVE-2007-6067, CVE-2007-4772,
CVE-2007-6601, CVE-2007-6600 and CVE-2007-4769.

Security: http://www.postgresql.org/about/news.905

Update PostgreSQL ports to the latest patch releases.

PR: ports/104075

Update PostgreSQL to 7.3.19, 7.4.17, 8.0.13, 8.1.9 and 8.2.4 respectively:

 The PostgreSQL Global Development Group has released updated versions
 for PostgreSQL 8.2 and all back versions to patch a privilege
 escalation exploit in SECURITY DEFINER functions.  All users of this
 feature are urged to update to the latest minor version and follow
 instructions on securing these functions as soon as possible.  This
 minor release also contains other fixes, so all users should plan to
 deploy it.

 Once you have updated, additional steps are required to secure your
 database against the exploit.  Please read the release notes at
 http://www.postgresql.org/docs/8.2/static/release.html and the
 TechDocs article at http://www.postgresql.org/docs/techdocs.77 on how
 to lock down your security definer functions, if you use them.

(Only the first 15 lines of the commit message are shown above )

Update PostgreSQL 8.x to 8.0.12, 8.1.8 and 8.2.3 respectively:

  The recent security release (8.0.11, 8.1.7, 8.2.2) has been withdrawn.
  It contained an issue which causes error with custom data types, type
  constraints and expression indexes. These upgrades fix the problem.

Update PostgreSQL with, amongst other things, two security fixes:

  A vulnerability allows suppressing the normal checks that a SQL
  function returns the data type it's declared to do. These errors can
  easily be exploited to cause a backend crash, and in principle might
  be used to read database content that the user should not be able to
  access. [CVE-2007-0555]

  A vulnerability involving changing the data type of a table column
  can easily be exploited to cause a backend crash, and in principle
  might be used to read database content that the user should not be
  able to access. [CVE-2007-0556]

The release includes a set of other fixes as well. Please see the
release information at
http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-7

Security: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0555
Security: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0556

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

Update PostgreSQL to latest versions: 8.1.5, 8.0.9, 7.4.14 and 7.3.16.

Release notes:
8.1.5  http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-5
8.0.9  http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-9
7.4.14 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-14
7.3.16 http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-16

Change name of the rc script from '010.pgsql.sh' to 'postgresql'

Add optional hierachy patch added for 7.4 and 8.1 ports.

Chase heimdal libs update [reported by several]

For 8.1+ the port enables autovacuum in ~pgsql/postgresql.conf when
running initdb

Cleanup the ports, moving pkg-message-* to files/pkg-message-*.in and
files/pgsql.sh.tmpl to files/postgresql.in. [ports/97767]

PR: ports/97767, submitted by delphij@FreeBSD.org

The update to handle different versions of ICU was not sufficient.
Update the patches to handle ICU version 3.6 and fall back to 3.4.

Update the patch to be more agnostic with regards to the version of icu.
It now links with icu-3.6 as well as the earlier versions.

Update all PostgreSQL to fix a security flaw

The PostgreSQL Global Development Group today released versions 8.1.4, 8.0.8,
7.4.13 and 7.3.15. This is an urgent update to close a security hole which
can permit a SQL injection attack on some applications running PostgreSQL.

Users are urged to apply the update as soon as reasonably possible. Since the
update affects client functionality, most driver projects will be updating
this week as well.

Because the security issue involved is complex, we have added a section in
Techdocs to explain it: http://www.postgresql.org/docs/techdocs.52. Please
read this first before applying the updates.

Also, fix rc_subr startup problems on FreeBSD-7.x.

Security:       http://www.postgresql.org/docs/techdocs.50
PR:             ports/95154

Minor release 8.1.3 patches security issue
Release Note:
http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-3

PR:             ports/93440
Submitted by:   Hirohisa Yamaguchi <umq@ueo.co.jp>

Add missing ) around SIZE statements.

Update postgresql with latest patch release.

A critical fix repairs an error in ReadBuffer that can cause data loss
due to overwriting recently-added pages.  This applies to the 8.1 and
8.0 branches on all platforms.

Note that this update might require a reindex of textual columns under
certain conditions; please see UPDATING.

Other fixes included are:
-- Character string locale comparison bug. This may require a REINDEX
    on text column indexes in some locales, such as Hungarian.
-- Prevent accidental changes of locale by plperl
-- Two fixes for Japanese encodings
-- Two fixes for COPY CSV
-- Fixes for functions returning RECORD
-- Fixes to autovacuum, dblink and pgcrypto

Update postgresql to 8.1.1

Submitted by:   Hirohisa Yamaguchi <umq@ueo.co.jp>
PR:             90443

Welcome to PostgreSQL 8.1.

The new release includes performance improvements and advanced SQL
features which will support bigger data warehouses, higher-volume
transaction processing, and more complex distributed enterprise
software.

Major new features in this release include:

      Roles:
           PostgreSQL now supports database roles, which simplify the
           management of large numbers of users with complex
           overlapping database rights.

      IN/OUT Parameters:

(Only the first 15 lines of the commit message are shown above )

Number of commits found: 22

14 vulnerabilities affecting 30 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities