On Thursday, March 21, 2013, wd <wd@wdicc.com> wrote: > 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. > > BTW: we use ominipitr. >
ok. tomorrow i will check that again. i think that when restore_command was enabled in the slave, the wal receiver proccess didnt appear (and i didnt see the changes inmediately happening in the slave).
I think you should use an other restore_command, in warm standby, the resotre_command will not exit and continue check xlog files and restore them, the streaming won't start when in restore. Try use cp instead of it.
