Re: Moving Pivotal's Greenplum work upstream

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Ewan Higgs <ewan_higgs(at)yahoo(dot)co(dot)uk>, "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Moving Pivotal's Greenplum work upstream
Date: 2015-03-17 20:06:46
Message-ID: 20150317200646.GG10492@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 17, 2015 at 02:09:34PM +0800, Craig Ringer wrote:
> It's a valid approach, but it's one that means it's unlikely to be practical to
> just cherry-pick a few features. There's sure to be a lot of divergence between
> the codebases, and no doubt Greenplum will have implemented infrastructure that
> overlaps with or duplicates things since added in newer PostgreSQL releases -
> dynamic shmem, bgworkers, etc. Even if it were feasible to pull in their
> features with the underlying infrastructure it'd create a significant
> maintenance burden. So I expect there'd need to be work done to move things
> over to use PostgreSQL features where they exist.

I think we would need to create a team to learn the Greenplum code and
move over what is reasonable. My guess is there is no desire in our
community to totally merge or maintain the Greenplum code --- of course,
that is just a guess.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2015-03-17 20:09:43 Re: Moving Pivotal's Greenplum work upstream
Previous Message Peter Eisentraut 2015-03-17 20:01:20 Re: ranlib bleating about dirmod.o being empty