ParAccel actually uses relatively little PostgreSQL code

I often find it hard to write about ParAccel’s technology, for a variety of reasons: With occasional exceptions, ParAccel is reluctant to share detailed information. With occasional exceptions, ParAccel is reluctant to say anything for attribution. In ParAccel’s version of an “agile” development approach, product details keep changing, as do plans and schedules.  (The gibe that ParAccel’s product […]

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

With occasional exceptions, ParAccel is reluctant to share detailed information.
With occasional exceptions, ParAccel is reluctant to say anything for attribution.
In ParAccel’s version of an “agile” development approach, product details keep changing, as do plans and schedules.  (The gibe that ParAccel’s product […]
Link to original post