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

From Bruce Momjian
Subject Re: "Hot standby"?
Date
Msg-id 200908112330.n7BNU7X17673@momjian.us
Whole thread Raw
In response to Re: "Hot standby"?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas wrote:
> On Tue, Aug 11, 2009 at 4:07 PM, Josh Berkus<josh@agliodbs.com> wrote:
> > So really, the "streaming replication" patch should be called "hot
> > standby",
> 
> No.  AIUI, hot standby means that when your primary falls over, the
> secondary automatically promotes itself and takes over.  It requires
> things like heartbeat monitoring and STONITH and is unrelated to
> anything we currently have under consideration.
> 
> > and the "hot standby" patch should be called "read only slaves"?
> 
> Yes.
> 
> > And *why* can't we call it log-based replication?
> 
> Well, we can call it anything we want.  For example, up until now
> we've been calling it "hot standby", even though that's clearly wrong.
> :-)

How about "streaming archive logging" for synchronous replication, and
"continuous archive slave" for read-only queries on a warm standby.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: WIP: getting rid of the pg_database flat file
Next
From: Greg Stark
Date:
Subject: Re: pgindent timing (was Re: [COMMITTERS] pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY)