| From: | Francisco Reyes <fran(at)reyes(dot)somos(dot)net> |
|---|---|
| To: | Michael Miyabara-McCaskey <mykarz(at)miyabara(dot)com> |
| Cc: | "'Justin Clift'" <aa2(at)bigpond(dot)net(dot)au>, <pgsql-novice(at)postgresql(dot)org>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [NOVICE] RE: Sizing of LARGE databases. |
| Date: | 2001-02-02 06:19:40 |
| Message-ID: | Pine.BSF.4.32.0102020116510.1877-100000@zoraida.reyes.somos.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-novice |
On Thu, 1 Feb 2001, Michael Miyabara-McCaskey wrote:
>
> And have you figured out what your upgrade path may be? For instance, I
> have not been able to find any evidence on how to make PostgreSQL scale
> (clustered nodes, parallel fail-over, high availability etc)
I believe 7.1 will have some level of replication, although it seems 7.2
will be the "replication" release.
I don't know how failover would work, but one possibility may be to use a
program like Understudy which monitors an IP address and if a machine dies
then it seems requests to the secondary machine. That combined with
replication from the database may help prevent down time and may also be
used to increase performance by using round-robin with Understudy.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantinos Agouros | 2001-02-02 06:39:41 | Re: Is Oracle really so much faster |
| Previous Message | Michael Miyabara-McCaskey | 2001-02-02 05:45:58 | RE: Sizing of LARGE databases. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Reyes | 2001-02-02 08:09:34 | Best method for large updates |
| Previous Message | Michael Miyabara-McCaskey | 2001-02-02 05:45:58 | RE: Sizing of LARGE databases. |