Re: 24x7x365 high-volume ops ideas - Mailing list pgsql-general

From Karim Nassar
Subject Re: 24x7x365 high-volume ops ideas
Date
Msg-id 1099536696.4813.186.camel@denali.cse.nau.edu
Whole thread Raw
In response to 24x7x365 high-volume ops ideas  ("Ed L." <pgsql@bluepolka.net>)
List pgsql-general
On Wed, 2004-11-03 at 18:10, Ed L. wrote:
> unfortunately, the requirement is 100% uptime all the time, and any
> downtime at all is a liability.  Here are some of the issues:

Seems like 100% uptime is always an issue, but not even close to
reality. I think it's unreasonable to expect a single piece of software
that NEVER to be restarted. Never is a really long time.

For this case, isn't replication sufficient? (FWIW, in 1 month I have to
answer this same question). Would this work?

* 'Main' db server up 99.78% of time
* 'Replicant' up 99.78% of time (using slony, dbmirror)
* When Main goes down (crisis, maintenance), Replicant answers for Main,
  in a read-only fashion.
* When Main comes back up, any waiting writes can now happen.
* Likewise, Replicant can be taken down for maint, then Main syncs to it
  when going back online.

Is this how it's done?

\<.


pgsql-general by date:

Previous
From: BarB
Date:
Subject: Re: RFD: comp.databases.postgresql.general
Next
From: Thomas F.O'Connell
Date:
Subject: Re: how to edit a function from psql?