From: | Ryan Kelly <rpkelly22(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | PostgreSQL, OLAP, and Large Clusters |
Date: | 2012-09-26 11:50:44 |
Message-ID: | 20120926115044.GA24075@llserver.lakeliving.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi:
The size of our database is growing rather rapidly. We're concerned
about how well Postgres will scale for OLAP-style queries over terabytes
of data. Googling around doesn't yield great results for vanilla
Postgres in this application, but generally links to other software like
Greenplum, Netezza, and Aster Data (some of which are based off of
Postgres). Too, there are solutions like Stado. But I'm concerned about
the amount of effort to use such solutions and what we would have to
give up feature-wise.
We love a lot of the features that we currently have that (I think)
would only be available with Postgres: arrays, hstore, gin/gist indexes,
extensions. Not to mention a lot of the other great SQL standard
features not available in other open-source databases, especially window
functions and CTEs.
Of course, migration to another solution is feasible (with enough
effort, of course), but given my experiences with Postgres and the
support provided by the community that is second to none, I'd very much
like to stay with PostgreSQL.
Thoughts?
-Ryan Kelly
From | Date | Subject | |
---|---|---|---|
Next Message | salah jubeh | 2012-09-26 14:21:57 | estemated number of rows and optimiser effeciency |
Previous Message | Devrim GÜNDÜZ | 2012-09-26 11:02:42 | Re: shared memory settings |