| From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
|---|---|
| To: | nasbyj(at)amazon(dot)com |
| Cc: | pgsql-www(at)postgresql(dot)org |
| Subject: | Re: Maliing list request: pgsql-forks@ |
| Date: | 2019-07-31 01:21:37 |
| Message-ID: | 20190731.102137.1533583987970715137.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
> 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.
Pgpool-II does not fall into "forks" mentioned above but it actually
forks part of PostgreSQL code (raw parser, memory manager and elog
stuffs). It has experienced part of the pains as other forks Jim
already mentioned:
Pain for forks due to high velocity of upstream commits
Backend static functions / structs
So +1 to create new ML.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2019-07-31 04:42:18 | Re: Maliing list request: pgsql-forks@ |
| Previous Message | Nasby, Jim | 2019-07-31 00:43:11 | Re: Maliing list request: pgsql-forks@ |