| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Mason S <masonlists(at)gmail(dot)com>, Oleg Bartunov <obartunov(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-09-01 17:46:17 |
| Message-ID: | 55E5E469.2030209@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09/01/2015 10:17 AM, Robert Haas wrote:
> On Tue, Sep 1, 2015 at 1:06 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>> Any sharding solution worth bothering with will solve some or all of the
>> above by extending our ability to process requests across multiple
>> nodes. Any solution which does not is merely an academic curiosity.
>
> I think the right solution to those problems is to attack them
> head-on. Sharding solutions should cater to use cases where using all
> the resources of one machine isn't sufficient no matter how
> efficiently we do it.
As long as "all the resources" != "just IO", I'm completely on board
with that. The reason I raised this is that the initial FDW-based
proposals pretty much scale IO and nothing else.
pg_shard also currently only scales IO, but they're working on that.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-09-01 17:47:03 | Re: Proposal: Implement failover on libpq connect level. |
| Previous Message | Joshua D. Drake | 2015-09-01 17:17:38 | Re: Horizontal scalability/sharding |