Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: High Avaliable in the PostgreSQL.
- From: Adam Tauno Williams <adamtaunowilliams(at)gmail(dot)com>
- To: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
- Cc: pgsql-admin(at)postgresql(dot)org
- Subject: Re: High Avaliable in the PostgreSQL.
- Date: Wed, 30 May 2007 18:12:02 -0400
On Wed, 2007-05-30 at 17:18 -0400, Andrew Sullivan wrote: > 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. Sure it can be done. Get two SANs that support replication, redundant high-speed WAN links, high end servers, large UPSs, and generators. It is just extremely expensive. :) -- Adam Tauno Williams, Network & Systems Administrator Consultant - http://www.whitemiceconsulting.com Developer - http://www.opengroupware.org
- Follow-Ups:
- Re: High Avaliable in the PostgreSQL.
- From: Andrew Sullivan
- Re: High Avaliable in the PostgreSQL.
- References:
- High Avaliable in the PostgreSQL.
- From: Fernando Ike de Oliveira
- Re: High Avaliable in the PostgreSQL.
- From: Andrew Sullivan
- High Avaliable in the PostgreSQL.
- Prev by Date: Re: Fwd: Out of Memory on Reindex
- Next by Date: Re: High Avaliable in the PostgreSQL.
- Previous by thread: Re: High Avaliable in the PostgreSQL.
- Next by thread: Re: High Avaliable in the PostgreSQL.
- Indexes: