From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
Cc: | "Nasby, Jim" <nasbyj(at)amazon(dot)com>, "pgsql-www(at)postgresql(dot)org" <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: Maliing list request: pgsql-forks@ |
Date: | 2019-07-30 13:39:38 |
Message-ID: | CANP8+jJicd4wYjrWTK2zGqJed-X5AcFqHef8GkXegj-2w+-eMQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Tue, 30 Jul 2019 at 14:36, Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
> On 7/30/19 8:16 AM, Simon Riggs wrote:
> > On Mon, 29 Jul 2019 at 22:57, Nasby, Jim <nasbyj(at)amazon(dot)com
> > <mailto:nasbyj(at)amazon(dot)com>> wrote:
> >
> > At pgCon we had an BoF for projects/companies that are maintaining
> > either forks of Postgres (ie: Aurora Postgres, EDB, Greenplum, BDR),
> > or extensions that interact heavily with internals (ie: Citus,
> > TimescaleDB). We’d like to have a mailing list to facilitate further
> > discussion in this area.____
> >
> >
> > BDR3 is not a fork of Postgres, but it is an extension.
>
> On that note, I'd be a +1 for "pgsql-extensions" as it would certainly
> help facilitate above suggested communication. It would be all
> encompassing of extensions, forks, etc.
>
Sounds like a better name and focus.
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Solutions for the Enterprise
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2019-07-30 13:41:51 | Re: Maliing list request: pgsql-forks@ |
Previous Message | Daniel Gustafsson | 2019-07-30 13:38:42 | Re: Maliing list request: pgsql-forks@ |