VMware has a strong commitment and belief that PostgreSQL will be a broadly used and popular IT technology for decades to come. This latest release marks a significant advancement that serves to underscore this assertion. First, VMware has chosen to standardize on a single common core, donating all advancements to the core to the community at large. As a result, the Postgres community at large will benefit from consistent, professional engineering that will ensure this project continues to advance with the demands of industry, in particular with cloud computing. The new VMware distribution, now shares the same common core as the open source PostgreSQL 9.2 release in September 2012.
This release builds on the PostgreSQL 9.1 most notably with the addition of new developer-oriented capabilities including JSON support, and enterprise IT-oriented capabilities such as cascading replication and index-only scans. These advancements solidify Postgres now as a database that can handle the vast majority of data types and workloads.
In addition to improvements to the core, VMware will continue to extend the vFabric Postgres distribution to better meet the demands of large scale web applications running on virtualized and cloud deployments. Continue reading →
Apache Derby is used for its RDBMS components, JDBC driver, query engine, and network server.
The partitioning technology of GemFire is used to implement horizontal partitioning features of vFabric SQLFire.
vFabric SQLFire specifically enhances the Apache Derby components, such as the query engine, the SQL interface, data persistence, and data eviction, as well as adding additional components like SQL commands, stored procedures, system tables, functions, persistence disk stores, listeners, and locators, to operate a highly distributed and fault tolerant data management cluster.
This post is meant to augment the knowledge base article, KB 2033940, published back in August.
Planning the Upgrade
We know platform changes can make an upgrade more difficult and certainly raise eyebrows. So, we’ve taken measures to help make the migration as seamless and simple as possible. So far, the cases we’ve seen take about an hour. As with any data migration, the greater the volume of database records, the longer it can take. Continue reading →
The next release of Hyperic is coming up soon and the biggest change is to the backend. In the next release, we will only support one database, namely PostgreSQL. Those of you who have been with Hyperic for a while as long as I have may be surprised considering our history with PostgreSQL, but, as you read though this blog, it will start to make sense.
History of PostgreSQL and Hyperic
For the last few years Hyperic has supported only two databases for production use at scale—Oracle and MySQL. This in itself was a big change since at one point, PostgreSQL was our bread and butter. Hyperic was originally designed on PostgreSQL 7.x. As an open source project, PostgreSQL has a very easy license for distribution. As a startup company we had to get our product out into the marketplace quickly and affordably, so therefore PostgreSQL made sense.
In this short Q&A, we get the perspective of Heikki Linnakangas who’s just joined VMware after being a senior software architect and contributing to PostgreSQL for six years.
1. You’ve been involved with PostgreSQL for a while, could you give us a bit about your background and how you’ve been involved?
It all started in 2003, when my second child was born. I was at home with the baby for a month or two, and thought it would be fun to take a look at how a DBMS works under the covers. I have done programming as a hobby since I was a kid, but had not had a chance to do much outside a work environment for some time. Continue reading →