I'm adding another table to my replication cluster, and created a new  
set with a single table in it.  The initial data copy failed because  
of some other transaction still being open, so it delayed.  The  
curious part is when the second (and every subsequent0 copy also  
failed, it issued a warning about "no transactin in progress" as shown  
below.  That warning is issued on every subsequent failure to  
subscribe the set.  (Turns out to be a vacuum that started just a  
minute prior to my subscribe!)


2007-12-30 12:02:18.645226500 DEBUG1 copy_set 3
2007-12-30 12:02:18.664078500 DEBUG1 remoteWorkerThread_4: connected  
to provider DB
2007-12-30 12:02:18.708326500 WARN   remoteWorkerThread_4:  
transactions earlier than XID 553658082 are still in progress
2007-12-30 12:02:18.711129500 WARN   remoteWorkerThread_4: data copy  
for set 3 failed - sleep 15 seconds
2007-12-30 12:02:33.713699500 DEBUG1 copy_set 3
2007-12-30 12:02:33.724418500 DEBUG1 remoteWorkerThread_4: connected  
to provider DB
2007-12-30 12:02:33.741157500 WARN   remoteWorkerThread_4:  
transactions earlier than XID 553658082 are still in progress
2007-12-30 12:02:33.741201500 WARN   remoteWorkerThread_4: data copy  
for set 3 failed - sleep 30 seconds
2007-12-30 12:02:33.741527500 WARNING:  there is no transaction in  
progress
2007-12-30 12:03:03.743469500 DEBUG1 copy_set 3
2007-12-30 12:03:03.752889500 DEBUG1 remoteWorkerThread_4: connected  
to provider DB
2007-12-30 12:03:03.759128500 WARN   remoteWorkerThread_4:  
transactions earlier than XID 553658082 are still in progress
2007-12-30 12:03:03.759269500 WARN   remoteWorkerThread_4: data copy  
for set 3 failed - sleep 60 seconds
2007-12-30 12:03:03.759571500 WARNING:  there is no transaction in  
progress