On Tue, Aug 11, 2009 at 11:19:18PM -0400, Robert Haas wrote:
> On Tue, Aug 11, 2009 at 9:44 PM, Greg Stark<gsstark@mit.edu> wrote:
> > On Tue, Aug 11, 2009 at 10:13 PM, Robert Haas<robertmhaas@gmail.com> 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.
> >
> > No! This is *not* what "hot standby" means, at least not in the Oracle world.
>
> I'm perplexed by this. For example: http://en.wikipedia.org/wiki/Hot_standby
>
> Admittedly, wikipedia is not an authoritative source, but I've always
> understood cold/warm/hot just as Peter described them upthread. Cold
> means it's on the shelf. Warm means it's plugged in, but you have to
> have to do something to get it going. Hot means it just takes over
> when needed.
After all this, perhaps we can at least conclude that calling it "cold",
"warm", or "hot" anything is confusing, because no one can agree on what that
means. I propose we leave off finding a naming that includes temperature.
--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com
