Comments on: ParAccel actually uses relatively little PostgreSQL code http://www.dbms2.com/2008/12/29/paraccel-actually-uses-relatively-little-postgresql-code/ Choices in data management and analysis Thu, 09 Feb 2012 21:52:17 +0000 hourly 1 http://wordpress.org/?v=3.0.3 By: ParAccel’s market momentum | DBMS2 -- DataBase Management System Services http://www.dbms2.com/2008/12/29/paraccel-actually-uses-relatively-little-postgresql-code/#comment-106163 ParAccel’s market momentum | DBMS2 -- DataBase Management System Services Sat, 03 Jan 2009 05:04:06 +0000 http://www.dbms2.com/?p=647#comment-106163 [...] my recent blog post, ParAccel is once again angry that I haven’t given it proper credit for it accomplishments. [...] [...] my recent blog post, ParAccel is once again angry that I haven’t given it proper credit for it accomplishments. [...]

]]> By: Curt Monash http://www.dbms2.com/2008/12/29/paraccel-actually-uses-relatively-little-postgresql-code/#comment-106089 Curt Monash Fri, 02 Jan 2009 04:44:35 +0000 http://www.dbms2.com/?p=647#comment-106089 Tom, Good point. :) CAM Tom,

Good point. :)

CAM

]]> By: Tom http://www.dbms2.com/2008/12/29/paraccel-actually-uses-relatively-little-postgresql-code/#comment-105954 Tom Wed, 31 Dec 2008 20:37:47 +0000 http://www.dbms2.com/?p=647#comment-105954 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. :) 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. :)

]]>