PostgreSQL 9.0 Released
PostgreSQL version 9.0 was released yesterday (Sept 20th). The 9.0 version of PostgreSQL includes a number of important new features, more new features in fact than any previous release.
Some of the new features found in 9.0 are:
- Streaming Replication - This allows one or more databases to be replicated from a primary database. The replication is asychronous but the lag between replications is short. Note that other 3rd party solutions for this have existed for some time.
- Hot Standby - This allows a second (duplicate) database to be designated as a standby in case the primary database goes down for some reason. The standby can also be used for read-only queries when the primary database is active, thereby providing a bit of load balancing. HotStandby works well with the new Streaming Replication feature.
- In-Place Upgrade - Using the pg_upgrade module databases created with older versions of PostgreSQL can be upgraded in-place without the need to dump and reload the database.
- Support for 64-bit Windows - For those of you that are familiar with whatever this "Windows" thing is.
I had an opportunity to talk to Robin Schumacher of EnterpriseDB and Josh Berkus of the PostgreSQL community. EnterpriseDB is a company that provides commercial versions of PostgreSQL. EnterpriseDB refers to itself as "The Enterprise Postgres Company." One of the things that I didn't realize about PostgreSQL is that it's not GPL licensed, rather it's licensed under the PostgreSQL License which is a license similar to the BSD or MIT licenses.
I asked a couple of minor things before I got to the big question:
- I asked about the usage figures for the different embedded languages available in PostgreSQL. PostreSQL has a built-in procedural programming language called PL/pgSQL, but it also supports extensions that allow you to use other languages such as Perl, Python, and Tcl (PL/Perl, PL/Python, and PL/Tcl respectively). Others may exist, but these are the ones documented with PostgreSQL itself. According to an onsite survey from a few years ago, PL/pgSQL is used by a bit more than half of all developers and the others have low double digit percentage usage.
- I also asked about the number of contributors that PostgreSQL has. Josh put that number at somewhere around 100 for core contributors and another 150 that contribute in other ways. He also mentioned that the project has been reorganizing itself to make it easier to contribute.
- And of course I asked about code size. Currently, PostgreSQL consists of about 300-400K lines of code.
Finally, I got to the big question, which was "How does PostgreSQL measure up against Oracle as an enterprise database?" Robin and Josh's answers follow:
Robin Schumacher (EnterpriseDB):
From an EnterpriseDB perspective, we're the leaders in providing an Oracle compatibility layer that people can use to run their Oracle applications on Postgres with little to no changes. Companies like IBM and Netezza use our Oracle compatibility layer inside their products to enable the same type of functionality.
With our Postgres Plus Advanced Server, we have everything from mirrored Oracle core features, support for Oracle's PL/SQL language, built in Oracle SQL packages, Oracle data dictionary and performance diagnostic compatibility, and more that lets database professionals use Advanced Server instead of Oracle as their database. We also support replicating data from Oracle to Postgres Plus Advanced Server so users can offload Oracle transactional data for reporting or other purposes on a more cost effective platform.
Josh Berkus (PostgreSQL community):
The limited benchmark results we have available, such as the SpecJAppserver benchmark published in 2007, indicate that performance on the two database systems is very similar, and that differences in performance are not enough to prevent migration. Beyond that, each database system has its strengths. Certainly, hundreds of users have migrated applications from Oracle to PostgreSQL successfully, and hundreds more work in a hybrid PostgreSQL-Oracle environment.
PostgreSQL 9.0 is superior for:
- Integration with 3rd-party open source tools
- Ability to extend functionality for specialized needs (such as biotech, security, or marketing analytics)
- Virtualized (cloud) deployments
Oracle 11 is superior for:
- Compatibility with existing proprietary vendor tools
- OLAP business intelligence
- Monitoring and administration tools
The last point is one which the PostgreSQL community is working actively on; each recent annual release has added several new or easier-to-use tools for monitoring and administration. Your primary reader audience will be particularly interested in the tools designed to integrate with Linux, such as pgTop (now available for Android as well) and pgFincore.
Mitch Frazier is an Associate Editor for Linux Journal.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide