gpdb

I was wondering if anyone had thought about using this to experiment with the planner. The engineering and support teams at Greenplum, a fork of Postgres, have a tool (minirepro[0]) which, given a sql query, can grab a minimal set of DDLs and the associated statistics for the tables involved in the query that can then be loaded into a "local" GPDB instance. Having the DDL and the statistics meant the team was able to debug issues in the optimizer (example [1]), without having access to a full set of data. This approach, if my understanding is correct, could be enabled in the browser with this Postgres WASM capability. [0] https://github.com/greenplum-db/gpdb/blob/6X_STABLE/gpMgmt/b... [1] https://github.com/greenplum-db/gpdb/issues/5740#issuecommen... (has an example output)

FWIW, if you're looking at PostgreSQL-at-humungo scale, there are a few options around. TimescaleDB, Citus (which Azure now offers as a service called Hyperscale DB) and there are others I always feel terrible for overlooking. I work for VMware and get along well with folks who work on Greenplum. It's still doing massive workloads with massive amounts of data for lots of customers, has the ability to operate over blob stores with predicate pushdowns and recently merged up to parity with the PostgreSQL 12 upstream[0]. It's the fruit of a six year effort to return to the upstream from a heavily modified fork of 8.3. A truly monumental effort. [0] https://github.com/greenplum-db/gpdb/commit/19cd1cf4b68faff2...

Link to greenplum db src code: https://github.com/greenplum-db/gpdb

other alternatives: now: * Pivotal Greenplum Database - is now Open Source : https://github.com/greenplum-db/gpdb later: * CitusDB 5.0 will be open source (2016Q1-Q2) : ( "An extension of PostgreSQL to be distributed/parallel query engine" ) https://twitter.com/frsyuki/status/667031289506062336 http://info.citusdata.com/CitusDB-5-Pre-Beta.html * PostgreSQL 9.6 will have a "Parallel Sequential Scans" : http://amitkapila16.blogspot.hu/2015/11/parallel-sequential-...

What's up with just a single commit since 2006? https://github.com/greenplum-db/gpdb/commits/master Why include all the really old commits, while squashing the most recent 10 years of commits into a single commit (6b0e52bead)?

It's Apache 2.0, so free as in beer and free as in speech. https://github.com/greenplum-db/gpdb/blob/master/LICENSE