> So what happens in those cases where the primary node gets in trouble
> but isn't actually dead yet?
Hmmm. Is this really a problem? Couldn't the secondary DRBD node simply
stop accepting replicated data from the primary node before firing up
postmaster? Then the postmaster on the primary DRBD node would only
write locally and not interfere with the secondary DRBD node.
Unless I am missing something this would be a valid problem with shared
storage but not with DRBD-like replicated storage. (As long as the
secondary node can stop replicating if it decides to do so.)
-Thomas
