| From: | Vivek Khera <vivek(at)khera(dot)org> |
|---|---|
| To: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Scalability |
| Date: | 2005-07-11 21:15:26 |
| Message-ID: | 11F50139-0B1C-4418-81C7-B6BC3D93DB90@khera.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jul 8, 2005, at 9:52 AM, postgresql(at)bryden(dot)co(dot)za wrote:
> I am trying to get information about the Scalability options
> available for
> PostgreSQL. Assuming you a database that has a huge volume of reads
> and
> writes happening, what options have you got to scale your database.
> Many
> commercial RDBMS' allow the clustering of Database servers and some
> other
> options. What options are available for PostgreSQL?
The website (contributed software area) lists some. But you'll need
to be more specific than "huge volume" to get reasonable answers from
this list (or preferably the postgres performance list).
Vivek Khera, Ph.D.
+1-301-869-4449 x806
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joseph Shraibman | 2005-07-11 22:10:23 | table locking and SELECT FOR UPDATE |
| Previous Message | Karl O. Pinc | 2005-07-11 20:04:33 | Re: A trigger that acts on a column with a given column |