Re: "Hot standby"?

On Tue, Aug 11, 2009 at 9:44 PM, Greg Stark<gsstark(at)mit(dot)edu> wrote:
> On Tue, Aug 11, 2009 at 10:13 PM, Robert Haas<robertmhaas(at)gmail(dot)com> wrote:
>> On Tue, Aug 11, 2009 at 4:07 PM, Josh Berkus<josh(at)agliodbs(dot)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.

But of course I guess Oracle can call their features what they want to...

> "log based replication", "read-only slaves", and "hot standby" are all
> 100% accurate descriptions of what the hot standby patch enables. I do
> like "read only slaves" because it's the most precise and meaningful.

Me too.

...Robert