Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: High Avaliable in the PostgreSQL.
- From: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
- To: pgsql-admin(at)postgresql(dot)org
- Subject: Re: High Avaliable in the PostgreSQL.
- Date: Wed, 30 May 2007 17:18:33 -0400
On Wed, May 30, 2007 at 04:42:08PM -0300, Fernando Ike de Oliveira wrote: > was 99,7% but considering the current necessities, change percentual > to 99,99%. I think in solution probability pgpool-2 or Heartbeat + > GFS. The PostgreSQL servers will be in different physical places. I would be very interested to see a set-up that can actually guarantee 99.99% uptime across a wide area link. What write speeds do you need in the database? What is your tolerance for loss of committed data? A -- Andrew Sullivan | ajs(at)crankycanuck(dot)ca "The year's penultimate month" is not in truth a good way of saying November. --H.W. Fowler
- Follow-Ups:
- Re: High Avaliable in the PostgreSQL.
- From: Adam Tauno Williams
- Re: High Avaliable in the PostgreSQL.
- References:
- High Avaliable in the PostgreSQL.
- From: Fernando Ike de Oliveira
- High Avaliable in the PostgreSQL.
- Prev by Date: Re: pg_dump: Error message from server: ERROR: compressed data is corrupt
- Next by Date: Re: pg_dump: Error message from server: ERROR: compressed data is corrupt
- Previous by thread: Re: High Avaliable in the PostgreSQL.
- Next by thread: Re: High Avaliable in the PostgreSQL.
- Indexes: