From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Chahine Hamila <chahine(dot)hamila(at)yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Subject: | Re: integration of pgcluster into postgresql |
Date: | 2006-08-27 07:40:30 |
Message-ID: | 87irkemxsh.fsf@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> That said, my company would feel more confortable with the idea that it's
>> part of the postgresql mainstream distro for many obvious reasons - or we
>> might drop postgresql altogether - which is why I'm proposing myself to do
>> the necessary work to integrate it in postgresql if there's interest.
>
> The core development team has only a very finite number of cycles available.
> Would you rather we spend our time on fixing pgcluster than on fixing the
> core Postgres database?
I'm beginning to wonder whether it would be better from a PR perspective to
rename pgfoundry to something like modules.postgresql.org. While "modules"
isn't necessarily technically right in postgresql vocabulary it's right in the
more general sense
And it doesn't imply the pieces of code are still in progress like
"projects.postgresql.org" might and doesn't give the impression that they're
living on their own without support from other postgres people like having a
separate domain does.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2006-08-27 09:24:07 | Re: [HACKERS] New XML section for documentation |
Previous Message | Peter Eisentraut | 2006-08-27 05:38:32 | Re: Autovacuum on by default? |