| From: | Qingqing Zhou <zhouqq(dot)postgres(at)gmail(dot)com> |
|---|---|
| To: | obartunov(at)gmail(dot)com |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Horizontal scalability/sharding |
| Date: | 2015-08-31 19:54:27 |
| Message-ID: | CAJjS0u13S+OSfCH89Bhjy2oft6_Ei6gWjLoL7ZUwcJdOaEWtuA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 31, 2015 at 2:12 AM, Oleg Bartunov <obartunov(at)gmail(dot)com> wrote:
>
> AFAIK, XC/XL has already some customers and that is an additional pressure
> on their development team, which is now called X2. I don't exactly know how
> internal Huawei's MPPDB is connected to XC/XL.
>
Huawei's MPPDB is based on PG-XC and tailored it more targeting OLAP scenarios.
The basic idea is that OLAP needs a shared nothing scale out
architecture for read and write. It needs ok-TP-performance, a
restricted set of functionality, and thus avoids some problems like
GTM being a central scaling bottleneck.
I advocate to merge PostgreSQL core with scale-out features, if we are
ready to face some long time functional discrepancies between the two
deployments.
Regards,
Qingqing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2015-08-31 20:12:01 | Re: Should \o mean "everything?" |
| Previous Message | Peter Eisentraut | 2015-08-31 19:23:23 | Re: Information of pg_stat_ssl visible to all users |