Commit graph

25 commits

Author SHA1 Message Date
Martin Matuska
39467857cc - Update to 8.4.2
Security:	CVE-2009-4034
Security:	CVE-2009-4136
Security:	http://portaudit.freebsd.org/e7bc5600-eaa0-11de-bd9c-00215c6a37bb.html
PR:		ports/141639
Submitted by:	Alexander Pyhalov <alp@rsu.ru>
Approved by:	ports-security (delphij)
2009-12-17 16:07:11 +00:00
Martin Matuska
38401795bf - Update to 8.4.1
- Set INTDATE on as default (this is default by PostgreSQL)

PR:		ports/139277
Submitted by:	Olli Hauer <ohauer@gmx.de>
Approved by:	maintainer timeout (2 months)
2009-12-02 22:21:27 +00:00
Palle Girgensohn
894d319504 Fix broken pkg-plist for gettext files.
Also, inform about pg_standby rather than autovacuum. [1]

PR:	136468 [1]
2009-07-08 20:31:53 +00:00
Palle Girgensohn
00c3beec39 Welcome PostgreSQL 8.4
After many years of development, PostgreSQL has become feature-complete in many areas.
This release shows a targeted approach to adding features (e.g., authentication,
monitoring, space reuse), and adds capabilities defined in the later SQL standards.
The major areas of enhancement are:

Windowing Functions
Common Table Expressions and Recursive Queries
Default and variadic parameters for functions
Parallel Restore
Column Permissions
Per-database locale settings
Improved hash indexes
Improved join performance for EXISTS and NOT EXISTS queries
Easier-to-use Warm Standby
Automatic sizing of the Free Space Map
Visibility Map (greatly reduces vacuum overhead for slowly-changing tables)
Version-aware psql (backslash commands work against older servers)
Support SSL certificates for user authentication
Per-function runtime statistics
Easy editing of functions in psql
New contrib modules: pg_stat_statements, auto_explain, citext, btree_gin

URL: http://www.postgresql.org/docs/8.4/interactive/release-8-4.html
2009-07-07 22:30:06 +00:00
Palle Girgensohn
4faeb886a5 Update PostgreSQL to latest versions.
URL: http://www.postgresql.org/about/news.1055

The PostgreSQL Project today released
updates to all active branches of the
PostgreSQL object-relational database
system, including versions 8.3.6,
8.2.12, 8.1.16, 8.0.20 and 7.4.24. These
updates include two serious fixes, for
autovacuum crashes in version 8.1 and
GiST indexing data loss in 8.3, and
those two versions should be updated as
soon as possible.

These update releases also include
patches for several low-risk security
holes, as well as up to 17 other minor
fixes, depending on your major version
of PostgreSQL. Included as well are
Daylight Savings Time changes for Nepal,
Switzerland and Cuba. See the release
notes for full details.

The first serious issue affects users
who are using version 8.1 with
Autovacuum, which will fail when XID
rollover is required. The second serious
issue can cause data loss when CLUSTER
is used with GiST indexes (such as full
text indexes) on version 8.3. Both
issues are fixed in these releases.
2009-02-10 11:59:15 +00:00
Palle Girgensohn
1c63d5a340 This time, *really* update to *latest* version of PostgreSQL, 8.3.5. 2008-11-07 18:07:50 +00:00
Palle Girgensohn
978e3de48f 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
2008-11-07 09:49:49 +00:00
Palle Girgensohn
89025407ac 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
2008-06-12 23:46:07 +00:00
Palle Girgensohn
6d85112973 Update to 8.3.1
Release notes:
http://developer.postgresql.org/pgdocs/postgres/release-8-3-1.html
2008-03-18 22:25:34 +00:00
Palle Girgensohn
fbbdeec687 Today the PostgreSQL Global Development Group releases the
long-awaited version 8.3 of the most advanced open source database,
which cements our place as the best performing open source
database. Among the performance features you'll be excited about in
8.3 are:

    * Heap Only Tuples
    * BGWriter Autotuning
    * Asynchronous Commit
    * Spread Checkpoints
    * Synchronous Scan
    * "Var-Varlena"
    * L2 Cache Protection
    * Lazy XID

8.3 also has a lot of cool features for PostgreSQL DBAs and developers, including:

    * CSV Logging
    * SQL/XML
    * MS Visual C++ support
    * ENUMs
    * Integrated Tsearch
    * SSPI & GSSAPI
    * Composite Type Arrays
    * pg_standby
2008-02-04 17:12:32 +00:00
Palle Girgensohn
98f3f95bd8 Update to RC2.
[1] Fix problem installing from package.

[2] Use DISTVERSION instead of PORTVERSION.
    (the port reports now correct version 8.3.r2)

[2] Enable more 8.3 features:
    - Add OPTION for the new XML data type (default: enabled)
    - Add OPTION for usage of system timezone data (default: included tzdata)

PR:		ports/119770 [1], ports/119561 [2]
Submitted by:	Artis Caune [1], Martin Matuska [2]
2008-01-22 14:08:48 +00:00
Palle Girgensohn
1d25499d3d 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
2008-01-07 13:51:57 +00:00
Palle Girgensohn
1577187ba7 Update to PostgreSQL 8.3 beta2.
http://www.postgresql.org/developer/beta

This is beta quality, don't use in production.

Approved by:	portmgr (erwin)
2007-11-01 07:10:04 +00:00
Palle Girgensohn
104aa6c048 Introducing the first beta of PostgreSQL 8.3
Note that this is a BETA VERSION of the PostgreSQL server.
Use it only for testing.
2007-10-15 15:32:19 +00:00
Ade Lovett
3e862d356d Fix plist
Approved by:	maintainer
2007-09-25 22:34:32 +00:00
Florent Thoumie
d4f0d0048a - Welcome X.org 7.2 \o/.
- Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}.
- Bump PORTREVISION for ports intalling files in ${X11BASE}.
2007-05-19 20:36:56 +00:00
Palle Girgensohn
0460921154 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.

 As always, application of a minor release does not require a dump and
 reload of the database.

 The frequency of security fixes recently is a result of increased
 scrutiny of the PostgreSQL code by government agencies and
 security-conscious companies.  Rapid turnaround on security patches
 is key to keeping PostgreSQL the most secure SQL database.  Your work
 and vigilance in applying the latest security updates ensures that
 there will never be a PostgreSQL "worm".

http://www.postgresql.org/docs/8.2/static/release-8-2-4.html
http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-9
http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-13
http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-17

http://www.postgresql.org/docs/techdocs.77

Security: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2138
2007-04-23 16:10:54 +00:00
Palle Girgensohn
6b11e89876 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
2007-01-09 16:29:35 +00:00
Palle Girgensohn
5b1dcdfc6f Welcome new release of the world's most advanced open source database:
PostgreSQL 8.2.0

Complete release notes are available at
http://www.postgresql.org/docs/current/static/release-8-2.html
2006-12-06 16:50:34 +00:00
Edwin Groothuis
d568611c3e eplace ugly "@unexec rmdir %D... 2>/dev/null || true" with @dirrmtry
Approved by:    krion@
PR:             ports/88711 (related)
2006-01-22 05:52:28 +00:00
Palle Girgensohn
d587b3a37a 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:
           PostgreSQL functions now support IN, OUT and INOUT
           parameters, which substantially improves support of complex
           business logic for J2EE and .NET applications.

      Two-Phase Commit (2PC):
           Long in demand for WAN applications and heterogeneous data
           centers using PostgreSQL, this feature allows
           ACID-compliant transactions across widely separated
           servers.

Some Performance Enhancements found in this release include:

      Improved Multiprocessor (SMP) Performance:
           The buffer manager for 8.1 has been enhanced to scale almost
           linearly with the number of processors, leading to significant
           performance gains on 8-way, 16-way, dual-core, and multi-core
           CPU servers.

      Bitmap Scan:
           Indexes will be dynamically converted to bitmaps in memory when
           appropriate, giving up to twenty times faster index performance
           on complex queries against very large tables.

      Table Partitioning:
           The query planner is now able to avoid scanning whole sections
           of a large table using a technique known as Constraint
           Exclusion.

       Shared Row Locking:
           PostgreSQL's "better than row-level locking" now supports even
           higher levels of concurrency through the addition of shared
           row locks for foreign keys.

For a more complete listing of changes in this release, please see the
Release Notes visible at:

http://www.postgresql.org/docs/current/static/release.html#RELEASE-8-1
2005-11-10 02:23:38 +00:00
Palle Girgensohn
ebc37b4280 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)
2005-05-11 00:40:15 +00:00
Palle Girgensohn
88413af3b8 In order to address a potential security hole recently identified with
the "LOAD" option, the PostgreSQL Global Development Group is
announcing the release of new versions of PostgreSQL.

Update to 7.3.9, 7.4.7 & 8.0.1.

Take the opportunity to reset PORTREVISION of slave ports.

Back out name change of startup script. The new script uses rc.subr(8),
and as such also uses rcorder(8). But, rcorder does not exist in FreeBSD
4.x. Hence rename the script it back to the top of the directory
list. [1]

The periodic script should of course be executable. [2]

[1] Noted by Niels Chr. Bank-Pedersen <ncbp at bank-pedersen dot dk>
[2] Noted by Fritz Heinrichmeyer <fritz.heinrichmeyer at fernuni-hagen dot de>
2005-02-03 09:30:27 +00:00
Palle Girgensohn
dde08c696b Say hello to postgresql-8.0. Some of the highlights of the new version
are savepoints (within transactions), point-in-time recovery and
tablespaces. Check out the release notes and the shiny new
PostgreSQL.org website at:

http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0

The port uses the new postgresql ports' layout and is split into a
server and a client part. The following knobs can be used by ports
depending on PostgreSQL:

# USE_PGSQL     - Add PostgreSQL client dependency.
#                 If no version is given (by the maintainer via the port or
#                 by the user via defined variable), try to find the
#                 currently installed version.  Fall back to default if
#                 necessary (PostgreSQL-7.4 = 74).
# DEFAULT_PGSQL_VER
#               - PostgreSQL default version. Can be overridden within a port.
#                 Default: 74.
# WANT_PGSQL_VER
#               - Maintainer can set an arbitrary version of PostgreSQL by
#                 using it.
# BROKEN_WITH_PGSQL
#               - This variable can be defined if the ports doesn't support
#                 one or more versions of PostgreSQL.

PR:		75344
Approved by:	portmgr@ (kris), ade & sean (mentors)
2005-01-31 00:36:16 +00:00
Ade Lovett
03e63e3bdb Another step along the road to the postgresql new world order.
Note that none of these ports are (yet) hooked into the tree,
and will not compile unless you set a specific environmental
variable.  This should be warning enough to leave well alone
for now :)

Submitted by:	maintainer
2004-11-23 19:15:12 +00:00