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
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
With Glom you can design table definitions and the relationships
between them, plus arrange the fields on the screen. You can edit
and search the data in those tables, and specify field values in
terms of other fields. It's as easy as it should be.
The design is loosely based on FileMaker Pro, with the added
advantage of separation between interface and data. Its simple
framework should be enough to implement most database
applications. Without Glom these systems normally consist of lots
of repetitive, unmaintainable code.
Glom-specific data such as the relationship definitions is saved
in the Glom document. Glom re-connects to the database server
when it loads a previous Glom document. The document is in XML
format.
Glom uses the PostgreSQL database backend but it can not edit
databases that it did not create, because it uses only a simple
subset of Postgres functionality.
Submitted by: adamw
Changes:
-supports passing an optional filehandle to the constructor
-optional autobless flag to preserve and restore blessed hashes
-various bug fixes
PR: 88519
Submitted by: maintainer
${PYTHON_SITELIBDIR} to ${WRKSRC}/../python to avoid compileall.py to touch
other apps' *.py files or there will be many leftover of *.pyc files. Bump
the PORTREVISION.
http://ruby-gnome2.sourceforge.jp/hiki.cgi?News_20051016_1
- Two new ports have been added, ruby-cairo and ruby-gtkmozembed.
- databases/ruby-libgda has been mark as BROKEN, because it still needs to
catch up w/ new libgda-2.0, so remove it from ruby-gnome2-all.
and new features. Don't believe me? Then see for yourself at
http://www.gnome.org/start/2.12/notes/en/.
DO NOT USE portupgrade by itself to upgrade to GNOME 2.12. Instead, use
the gnome_upgrade.sh script from
http://www.marcuscom.com/downloads/gnome_upgrade212.sh. This script will
circumvent some potential pitfalls users can see if they use portupgrade
by itself.
In keeping with tradition, GNOME 2.12 for FreeBSD comes with a special
splash screen. The winner of this release's contest is
Dominique Goncalves <dominique.goncalves@gmail.com>. His splash screen
was inspired by http://art.gnome.org/contests/2.12-splash/83.
The FreeBSD GNOME Team would lank to thank the following users for
their contributions to this release:
Matthew Luckie <mjl@luckie.org.nz>
ade
sajd on #freebsd-gnome
Caelian on #freebsd-gnome
mnag
Yasuda Keisuke <kysd@po.harenet.ne.jp>
Mark Hobden <markhobden@gmail.com>
Sergey Akifyev <asa@agava.com>
Andreas Kohn
For more information on GNOME on FreeBSD, checkout
http://www.FreeBSD.org/gnome/. The 2.12 documentation will be
posted shortly.
PostgreSQL's clients(front ends) and servers(back ends). A PostgreSQL client can
connect to pgpool as if it were a standard PostgreSQL server.
pgpool caches the connection to PostgreSQL server to reduce the overhead to
establish the connection to it.
WWW: http://pgpool.projects.postgresql.org/
PR: 87701
Submitted by: Choe, Cheng-Dae <whitekid@gmail.com>
===> p5-Some-Module-0.7 Port requires perl 5.6.x or later. Install
lang/perl5 then try again.
to:
===> p5-Some-Module-0.7 requires perl 5.6.x or later. Install
lang/perl5 then try again.
Approved by: silence on -ports
