On 11/20/2004 9:55 PM, Marc G. Fournier wrote:

> What does this mean, on the subscriber machine?  Replication appears to be 
> working fine, even with it:
> 
> : CONFIG main: slon version 1.0.5 starting up 
> : CONFIG main: local node id = 2 
> : CONFIG main: loading current cluster configuration 
> : CONFIG storeNode: no_id=1 no_comment='Node 1' 
> : CONFIG storePath: pa_server=1 pa_client=2 pa_conninfo="dbname=ams host=db.hub.org user=pgsql" pa_connretry=10 
> : CONFIG storeListen: li_origin=1 li_receiver=2 li_provider=1 
> : CONFIG storeSet: set_id=1 set_origin=1 set_comment='Distributed DNS Database' 
> : WARN   remoteWorker_wakeup: node 1 - no worker thread 
> : CONFIG storeSubscribe: sub_set=1 sub_provider=1 sub_forward='f' 
> : WARN   remoteWorker_wakeup: node 1 - no worker thread 
> : CONFIG enableSubscription: sub_set=1 
> : WARN   remoteWorker_wakeup: node 1 - no worker thread 
> : CONFIG main: configuration complete - starting threads 
> : CONFIG enableNode: no_id=1

That message should probably be removed ... it only happens during the 
startup when the internal configuration didn't cause a worker thread yet 
to be started, but changes in the in memory configuration info try to 
wake up an "eventually" existing one. At least the message should be 
downgraded to a debug message.


Jan

> 
> ----
> Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
> Email: scrappy at hub.org           Yahoo!: yscrappy              ICQ: 7615664
> _______________________________________________
> 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 #