On 9/22/2004 8:05 AM, Matthew Wild wrote:

> I'm trying to replicate some databases from a PostgreSQL 7.3.4 and 7.3.7
> installation on Tru64 V5.1 master to a 7.4 installation on SuSE 9.1 Linux.  
> I can get the slonik commands to configure a cluster and subscribe to a
> set, but when I start the slon daemon on the master node (tru64) I get the 
> following output
> 
> MASTER : 
> CONFIG main: local node id = 1
> CONFIG main: loading current cluster configuration
> CONFIG storeNode: no_id=2 no_comment='Slave node, ukssdc-db1'
> CONFIG storePath: pa_server=2 pa_client=1 pa_conninfo="dbname=digisondes
> host=ukssdc-db1.stp.rl.ac.uk user=postgres" pa_ connretry=10
> CONFIG storeListen: li_origin=2 li_receiver=1 li_provider=2
> CONFIG storeSet: set_id=1 set_origin=1 set_comment='digisondes tables'
> CONFIG main: configuration complete - starting threads
> CONFIG enableNode: no_id=2
> ERROR remoteListenThread_2: "select ev_origin, ev_seqno, ev_timestamp,
> ev_minxid, ev_maxxid, ev_xip, ev_t ype, ev_data1, ev_data2, ev_data3,
> ev_data4, ev_data5, ev_data6, ev_data7, ev_data8 from "_w
> dc_digisondes".sl_event e where (e.ev_origin = '2' and e.ev_seqno > '0')  
> order by e.ev_origin, e.ev_seqno" - could not r eceive data from server:
> Operation now in progress
> ERROR remoteListenThread_2: "select ev_origin, ev_seqno, ev_timestamp,
> ev_minxid, ev_maxxid, ev_xip, ev_t ype, ev_data1, ev_data2, ev_data3,
> ev_data4, ev_data5, ev_data6, ev_data7, ev_data8 from "_w
> dc_digisondes".sl_event e where (e.ev_origin = '2' and e.ev_seqno > '0')  
> order by e.ev_origin, e.ev_seqno" - could not r eceive data from server:
> Operation now in progress
> ERROR ...
> 
> and on the 
> 
> SLAVE : 
> 
> CONFIG main: local node id = 2
> CONFIG main: loading current cluster configuration
> CONFIG storeNode: no_id=1 no_comment='Master node, c1'
> CONFIG storePath: pa_server=1 pa_client=2 pa_conninfo="dbname=digisondes 
> host=c1.stp.rl.ac.uk user=postgres" pa_connretr
> y=10
> CONFIG storeListen: li_origin=1 li_receiver=2 li_provider=1
> CONFIG storeSet: set_id=1 set_origin=1 set_comment='digisondes tables'
> 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 main: configuration complete - starting threads
> CONFIG enableNode: no_id=1
> 
> 
> Presumably this is the --enable-thread-safety feature of libpq seen on 
> Solaris and AIX. Is there a fix for Postgresql version 7.3.4/7.3.7?

I still have to produce a backpatch of the 7.4.x version of this.


Jan

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