[PATCH 3/4] When doing a fail node where the failed node is not a provider of the backup node we need to delete any subscribe entries that are used to forward data to the backup node. These will not be needed when the backup node becomes the new origin. Until that happens they get in the way of the FAILOVER_SET message that will be posted on the 'most ahead node' but iwth an origin of the old origin from getting to this node.

Fri Jul 30 12:55:17 PDT 2010

---
 src/backend/slony1_funcs.sql |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/src/backend/slony1_funcs.sql b/src/backend/slony1_funcs.sql
index 8dcaf03..8c77c8d 100644
--- a/src/backend/slony1_funcs.sql
+++ b/src/backend/slony1_funcs.sql
@@ -1277,8 +1277,12 @@ begin
 								where pa_server = p_backup_node
 								  and pa_client = @NAMESPACE at .sl_subscribe.sub_receiver
 						);
+			delete from @NAMESPACE at .sl_subscribe
+					where sub_set = v_row.set_id
+						and sub_receiver = p_backup_node;				
 		end if;
 	end loop;
+	
 
 	-- Rewrite sl_listen table
 	perform @NAMESPACE at .RebuildListenEntries();
-- 
1.6.3.3


--------------020106060301020405000608
Content-Type: text/x-patch;
 name="0004-Bug-136.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="0004-Bug-136.patch"

