From: | "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu> |
---|---|
To: | Alessandro Gagliardi <alessandro(at)path(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Planning a Large RDBMS |
Date: | 2012-06-15 18:42:33 |
Message-ID: | 20120615184233.GI6547@aart.rice.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Fri, Jun 15, 2012 at 11:11:17AM -0700, Alessandro Gagliardi wrote:
> Hi folks,
>
> We've been using MongoDB for the past couple years and are talking about
> moving to a more traditional (i.e. stable) database system for OLTP. I've
> been using RDBMS for OLAP already, but the demands are somewhat different.
> But we figure, if Facebook can do it, we can. The expertise around here is
> more suited for MySQL, but I, for one, am fond of the features in Postgres
> that you can't find in MySQL. Our Mongo system is sharded across 11 logical
> nodes on Amazon's EC2. Our database is in the hundreds of gigabytes (i.e.
> too big for memory on one machine) and we can expect it to exceed
> a terabyte before too long. We have the distinct advantage of being able to
> plan this from the ground up. I've read a bit about partitioning and table
> spaces, but from what I can tell, those solutions still require the
> database to be hosted by a single machine which may not suffice for our
> purposes.
>
> I realize this is a big question, and possibly too big to answer here. But
> I would be grateful even for some website or chapter recommendations.
>
> Thank you in advance,
> -Alessandro
He Alessandro,
I just saw an announcement for the 1.0 release of Postgres-XC which
may fit your use case.
Regards,
Ken
From | Date | Subject | |
---|---|---|---|
Next Message | Alessandro Gagliardi | 2012-06-15 18:44:51 | Re: Planning a Large RDBMS |
Previous Message | Alessandro Gagliardi | 2012-06-15 18:11:17 | Planning a Large RDBMS |