Re: "Hot standby"?

As I see it we potentially have the following modes to deal with:

Archive file mode     asynchronous  archive
Archive file mode     asynchronous  standby slave
Streaming mode      asynchronous  standby slave
Streaming mode      synchronous    standby slave
Archive file mode     asynchronous  read-only slave
Streaming mode      asynchronous  read-only slave
Streaming mode      synchronous    read-only slave

By "standby slave" I mean a server which is constantly in recovery
mode but isn't open for connections. This is what we (and Oracle) have
been calling a warm standby. By "read-only slave" I mean a server
which is open for connections and can handle read-only queries, which
as I mentioned Oracle calls a hot standby. Note that *all* of these
are "log-based replication".

I'm not actually certain we can handle streaming synchronous mode to a
standby slave. Does the slave need to have connections enabled to
handle feeding wal sync status to the master?

I don't see any particular reason to come up with names for each of
these combination of modes. I'm pretty happy just saying there are
three different configuration options and certain options depend on
other options so only certain combinations are legal.

-- 
greg