On 10/30/2004 10:20 AM, Ed L. wrote:

> On Friday October 29 2004 11:55, Ed L. wrote:
>> I'm seeing these messages as I attempt to start replication with 1.0.5
>> ...
>>
>> DEBUG1 remoteWorkerThread_1: connected to provider DB
>> WARN   remoteWorkerThread_1: transactions earlier than XID 41058487 are
>> still in progress
>> WARN   remoteWorkerThread_1: data copy for set 1 failed - sleep 60
>> seconds
> 
> After more than 8 hours, nothing has been replicated, and the above messages 
> continue.  This system has over 100 connections; what is the easiest way to 
> identify whose holding up the replication?  Would it be possible for slony 
> to actually help in identifying the backend that has the outstanding 
> transactions?

A combination of pg_locks together with pg_stat_activity (if that's 
enabled) or a ps(1) would probably give you some idea what's sitting 
there in an endless, idle transaction.


Jan

> 
> Ed
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #