Skip site navigation (1) Skip section navigation (2)

Bizgres MPP 2.1 Available for Public Download

Posted on Feb. 26, 2006

GreenPlum Inc. has released Bizgres MPP 2.1, the scalable data warehousing clustered version of PostgreSQL. It is available for trial download on the Bizgres Network website.

Bizgres MPP 2.1 is based on PostgreSQL 8.1 and will support most PostgreSQL applications out of the box. It allows you to spread your database across multiple servers, and run parallelized queries over databases up to 100 terabytes in size, with data read rates over 10GB/second. Bizgres MPP is built on a fault-tolerant shared-nothing architecture which allows for cluster expansion, using commodity hardware.

The new Bizgres Network website (BGN.greenplum.com), Greenplum's customer web portal, is open for free registration and downloads today. The Bizgres Network offers downloads, an extensive knowledge base, and online support for both Bizgres MPP and open source Bizgres Database. Try it out, GreenPlum will even provide 30 days free support.

For those of you who participated in the Bizgres MPP 2.0 beta, new features include:

  • PostgreSQL 8.1 compatibility ­ now faster and better concurrency with the latest release of PostgreSQL
  • Improved Transaction Throughput ­ supports mixed light OLTP and DSS workloads more effectively, with hundreds of statements per second of throughput
  • Optimized for the latest Intel/AMD CPUs ­ all CPUs work together to answer each query, even on single hosts
  • Improved Fault-Tolerance and Back-Up and Restore utilities

GreenPlum Inc. of San Mateo is a sponsor of the PostgreSQL and Bizgres open source projects. The open source Bizgres Database and Bizgres Clickstream code remain available at www.bizgres.org. Bizgres MPP is Greenplum's commercial offering.

For questions from the PostgreSQL community, please contact Josh Berkus. Members of the press should contact Emily Swanson.

This post has been migrated from a previous version of the PostgreSQL website. We apologise for any formatting issues caused by the migration.


Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group