Re: Maliing list request: pgsql-forks@
От | Jonathan S. Katz |
---|---|
Тема | Re: Maliing list request: pgsql-forks@ |
Дата | |
Msg-id | fb83d409-e02c-a1c1-b9af-40fe79e957b8@postgresql.org обсуждение исходный текст |
Ответ на | Re: Maliing list request: pgsql-forks@ (Daniel Gustafsson <daniel@yesql.se>) |
Ответы |
Re: Maliing list request: pgsql-forks@
|
Список | pgsql-www |
On 7/30/19 8:38 AM, Daniel Gustafsson wrote: >> On 30 Jul 2019, at 15:35, Jonathan S. Katz <jkatz@postgresql.org> wrote: >> >> On 7/30/19 8:16 AM, Simon Riggs wrote: >>> On Mon, 29 Jul 2019 at 22:57, Nasby, Jim <nasbyj@amazon.com >>> <mailto:nasbyj@amazon.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. > > Or perhaps pgsql-distributions@, to make it even clearer that it’s a forum for > all postgres derived distributions regardless of technical implementation. (and while I do like blue for the color of the bike ;) I think that "distributions" is too close to "packaging" and could be confusing. Why I suggested "-extensions" is that it appears to be inclusive of things that augment PostgreSQL abilities, be they actual PG extensions or forks. Jonathan
Вложения
В списке pgsql-www по дате отправления: