Re: "Hot standby"? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: "Hot standby"?
Date
Msg-id 603c8f070908111014t64f6bae7sb025545205290dd1@mail.gmail.com
Whole thread Raw
In response to Re: "Hot standby"?  (Josh Berkus <josh@agliodbs.com>)
Responses Re: "Hot standby"?  (Gianni Ciolli <gianni.ciolli@2ndquadrant.it>)
List pgsql-hackers
On Tue, Aug 11, 2009 at 1:08 PM, Josh Berkus<josh@agliodbs.com> wrote:
> I believe we're just copying Oracle's terminology.  While that
> terminology is not consistent, it is understood by the industry.  Oracle
> defined their Hot Standby to have both asynchronous and synchronous modes:
> http://www.oracle.com/technology/products/rdb/htdocs/dbms/hotstandby.html

I think that you are wrong.  Hot Standby is described in that document
as a way of replication the database and providing failover in the
event that the master dies.  This feature has to do with allowing
queries to be executed on the slave, which is not discussed in that
document.

...Robert


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Any tutorial or FAQ on building an extension?
Next
From: Robert Haas
Date:
Subject: Re: Re: pgindent timing (was Re: [COMMITTERS] pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY)