John Bleichert wrote on Wednesday, June 24, 2015 4:21 PM: Ø Would I then configure that new server instance as a standby server as per doc section 18.6? Ø Or should I just setup the standby server first? Having re-read 18.6 I think this is what I want. I may be wrong but I’m not sure a master-standby setup will work for you given that you mentioned different OSes. Then again, I’m not sure it won’t either. Section 25.2.1 says, “It is usually wise to create the primary and standby servers so that they are as similar as possible, at least from the perspective of the database server. In particular, the path names associated with tablespaces will be passed across unmodified, so both primary and standby servers must have the same mount paths for tablespaces if that feature is used. […] In any case the hardware architecture must be the same — shipping from, say, a 32-bit to a 64-bit system will not work.” (And I am not sure whether this applies to file-based log shipping, streaming replication, or both.) At least the docs did not say that different OSes will not work at all. If you do happen to use tablespaces and exactly one of your different OSes is Windows then the thing with the unmodified path names will not work (obviously). |
