From: | Jorge Godoy <jgodoy(at)gmail(dot)com> |
---|---|
To: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
Cc: | Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Multiple DB join |
Date: | 2006-08-15 13:25:00 |
Message-ID: | 87ejvi6sib.fsf@ieee.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Andrew Sullivan <ajs(at)crankycanuck(dot)ca> writes:
> On Tue, Aug 15, 2006 at 09:01:03AM -0300, Jorge Godoy wrote:
>> I can think that spreading processing requirements should be one. And
>> distributing load another one. Disk space can be solved with new disks and
>> tablespaces, but we can't yet distribute the load through several servers
>> without partitioning.
>
> The cost of inter-node communication isn't nothing, though. It
> strikes me as at least possible that the overhead of dblink is going
> to be larger than whatever gains one makes from adding a new server.
> For only 20M rows, I find it pretty hard to believe the gain is going
> to be demonstrable.
I totally agree with you. But when your base grows, it might start getting
interesting.
I'd like to see some sort of data partitioning in PostgreSQL.
--
Jorge Godoy <jgodoy(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2006-08-15 13:49:47 | Re: Query response time |
Previous Message | Andrew Sullivan | 2006-08-15 13:18:20 | Re: Multiple DB join |