December 29, 2008

ParAccel actually uses relatively little PostgreSQL code

I often find it hard to write about ParAccel’s technology, for a variety of reasons:

ParAccel is quick, however, to send email if I post anything about them they think is incorrect.

All that said, I did get careless when I neglected to doublecheck something I already knew. The conclusion of this post isn’t really consistent with what ParAccel told me way back in February, 2007 about how much or how little PostgreSQL code they use in their product. As ParAccel just emailed me — for attribution 🙂 —

Our C-MPP execution engine on our compute nodes is written from scratch from the ground up.  There is a thin layer of postgres on the leader node (for parsing, initial planning, ODBC, JDBC), but 90% of the leader is also new code.

I’d guess that’s a lot like how Infobright and Kickfire use MySQL, although I wouldn’t want to commit to exact details. 😉 By way of comparison, PostgreSQL-compatible Vertica actually uses no PostgreSQL code at all, whereas row-based Greenplum and Aster Data make heavy use of PostgreSQL code.  DATAllegro (now Microsoft Project Madison) makes heavy use of the underlying row-based general-purpose DBMS. Netezza made some use of PostgreSQL code when it started years ago — but not, I think, to nearly the extent Greenplum and Aster Data did.


3 Responses to “ParAccel actually uses relatively little PostgreSQL code”

  1. Tom on December 31st, 2008 4:37 pm

    I’ve probably carried on about this before, but…

    Last I knew Netezza used PG pretty much as-is on the head node to store the data dictionary and other metadata. The actual code that runs on the SPUs is dynamically generated on the fly on the head node, so that can in no way be borrowed from PG. 🙂

  2. Curt Monash on January 2nd, 2009 12:44 am


    Good point. 🙂


  3. ParAccel’s market momentum | DBMS2 -- DataBase Management System Services on January 3rd, 2009 1:04 am

    […] my recent blog post, ParAccel is once again angry that I haven’t given it proper credit for it accomplishments. […]

Leave a Reply

Feed: DBMS (database management system), DW (data warehousing), BI (business intelligence), and analytics technology Subscribe to the Monash Research feed via RSS or email:


Search our blogs and white papers

Monash Research blogs

User consulting

Building a short list? Refining your strategic plan? We can help.

Vendor advisory

We tell vendors what's happening -- and, more important, what they should do about it.

Monash Research highlights

Learn about white papers, webcasts, and blog highlights, by RSS or email.