LWN.net Logo

PostgreSQL 8.1 Released

From:  josh-AT-postgresql.org
To:  pr-AT-lwn.net
Subject:  PostgreSQL 8.1 Released
Date:  Tue, 8 Nov 2005 05:54:38 -0400 (AST)

8 November 2005, Frankfurt, Germany (Open Database Conference):  
The PostgreSQL Global Development Group proudly announces the release of
PostgreSQL 8.1, further extending PostgreSQL's lead as the most advanced
open source database management system. Designed, built, and tested by a 
large and thriving community and backed by a growing number of corporate
sponsors and support companies, version 8.1 will expand the scope of 
PostgreSQL application development.  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.

These features will continue the adoption trend established by the previous
release. Version 8.0 has been downloaded one million times in its first seven
months, which compares with about 300,000 over a similar period for the prior
release.

"The project is clearly accelerating in the minds of database users," 
said Lance Obermeyer, Director of Products at Pervasive Software, 
one of PostgreSQL's corporate sponsors. "Given the growing interest
in open source infrastructure software, we're expecting PostgreSQL
to pick up even more steam."

New Advanced Database Features
-------------------------------

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.

Performance Enhancements
--------------------------

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. This also helps simplify database management
by greatly reducing the need for multi-column indexes.

Table Partitioning: the query planner is now able to avoid 
scanning whole sections of a large table using a technique known
as Constraint Exclusion. Similar to the Table Partitioning found
in other database management systems, this feature improves both
performance and data management for multi-gigabyte tables.

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.  Shared locks will improve
insert and update performance on many high-volume OLTP applications.

"PostgreSQL 8.1 offers a huge performance increase pretty much
across the board, [on our] dual processor Opteron production
servers," said Merlin Moncure, Database Administrator for 
Reliable Computer Solutions. "More specifically, I'm seeing 
around 20% reduction in run times for simple queries and 
an additional 20% reduction in CPU load, for a staggering 20-40% 
improvement in server load characteristics."  

There are more than 120 other enhancements, some of which are detailed on our
8.1 presskit: http://www.postgresql.org/about/press/presskit81.html.en

About PostgreSQL
------------------
PostgreSQL is the collective work of hundreds of developers,
building on twenty years of development which started at the University
of California at Berkeley. With its long-time support of an enterprise level
feature set including transactions, functions, triggers, and subqueries,
PostgreSQL is being used by many of today's most demanding businesses and
government agencies. PostgreSQL is distributed under a BSD license, which
allows use and distribution without fees for both commercial and
non-commercial applications.


(Log in to post comments)

Thanks!

Posted Nov 8, 2005 19:02 UTC (Tue) by bojan (subscriber, #14302) [Link]

Brilliant, thanks PostgreSQL Team! Looking back to 6.x days (whey I hopped on board), the software is better by leaps and bounds and new releases never disappoint. Looking forward to taking 8.1 for a spin :-)

PS. So that's why today's Rawhide bumped up my PostgreSQL ;-)

PostgreSQL 8.1 Released

Posted Nov 8, 2005 23:21 UTC (Tue) by proski (subscriber, #104) [Link]

This completly messes the plans for Ingress to become "the leading open source database supplier" :-)

Congratulations to the PostgreSQL users and developers! Two-Phase Commit is a big deal - I know someone who was using Oracle because PostgreSQL didn't have this feature.

PostgreSQL 8.1 Released

Posted Nov 9, 2005 1:37 UTC (Wed) by yem (guest, #1138) [Link]

Huge congrats and thanks to all the devs, documenters and testers! 8.1 is an impressive improvement over 7.x. The multiple condition index optimisations have seen queries which typically took 20-30 minutes to run on 7.3 complete in around 10 seconds on the same hardware. Night and day.

Now if we can just get a properly documented method for implementing PITR (or slony1's new log shipping feature).. then I can kiss Sybase good bye.

PostgreSQL 8.1 Released

Posted Nov 9, 2005 19:05 UTC (Wed) by dlang (subscriber, #313) [Link]

I thought that PITR was a feature of 8.1, is it just missing documentation or did it get pulled prior to release?

PITR included

Posted Nov 10, 2005 1:53 UTC (Thu) by yem (guest, #1138) [Link]

It's there - just poorly documented. For example, to ensure you're taking a full backup you need to copy the CURRENT WAL log file. But the docs do not specify a way to tell which file that might be out of the dozen files in pg_xlog/. A reference backup and restore script would be great to have.

Still, the PITR system requires you to backup and restore the whole server in one go - you cannot do just one database (AFAIK). Slony1 appears to be able to handle database by database, but again the log shipping feature is underdocumented and geared towards replication. Slony is also fairly invasive in that it adds columns to your tables where required and requires all tables to be specified in slonik config/commands.

Nobody thinks of backups :(

Speed

Posted Nov 10, 2005 19:05 UTC (Thu) by hisdad (subscriber, #5375) [Link]

Hi, I've been fiddling with dspam and pg for a little while.
My test is a body of 1390 spam. The dspam doc recommends mysql, citing performance figures that I never saw with pg.
With pg 8.0.4, on a reiserfs filesystem, learning would take 94minutes.
Recently I tried changing the filesystem to XFS. The time dropped to 52minutes.
This is certainly to do with the fdatasync() operation.
Yesterday I upgraded to 8.1 The time has dropped to 6 minutes.
Its simply amazing.
--John

Copyright © 2005, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds