You can combine warm standby and streaming, we do this in our product database.
When the standby is to far from the master, the slave will try to use restore_command to restore the database(warm standby), when the standby catch up the master, the steaming will working again.
i'm installing a streaming replication master-slave setup in ubuntu 12.04 LTS, with postgresql 9.1
the tutorials and the documentation are a very good start point, but i have one question related to some fine grained configurations.
it is said that i should stop the master db in order to make de starting backup, OR run pg_start_backup and keep the archive files for the slave to catch up. if i dont do this, maybe the slave stays far behind the master and the wal_segments arent enough to start the replication.
if I understand this right, i can "combine" the old "warm standby" configs of archive_command in the master and restore command in the slave to ensure that the slave will have the necessary info to start the replication.
i mean, i can have both configurations enabled?
right now, my streaming replication setup has this configs: