projects / slony1-engine.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 6c7c912) | patch
1. The update sl_subscribe statement was duplicated,
authorSteve Singer <ssinger@ca.afilias.info>
Fri, 17 Sep 2010 14:49:43 +0000 (10:49 -0400)
committerSteve Singer <ssinger@ca.afilias.info>
Fri, 17 Sep 2010 20:13:41 +0000 (16:13 -0400)
commit7970189ec93faf3ee71cf49e97529980bbd219aa
tree6331dd529341f58ceb3d362da39bc9e5b68d47fatree
parent6c7c91252f437e9dd5c86b6f2a0f92840c135b6dcommit | diff
1. The update sl_subscribe statement was duplicated,
   the exact same SQL was listed twice.
2. Do not delete the sl_subscribe row for the backup node.
   We were finding that a slave could end up with data the
   backup node did not have when it became a master because
   the backup node was ignoring the sync because it didn't
   think it had a provider.

This reverts parts of d50fba024aac79020549973e98a4ea9d5bccdab5
src/backend/slony1_funcs.sql diff | blob | blame | history
slony1: replication system with single master replicating to multiple subscribers supporting cascaded replication