Nigel Bishop wrote:

>Hi,
>
>This is the first time I've tried to set up replication using slony and
>I would appreciate someone's help please:
>
>Slony 1.0.5
>PG 8.0.2
>Solaris 8
>
>I configured slony with the following:
>
>$ ./configure --with-pgsourcetree=/home/postgres/802src/postgresql-8.0.2
>--enable-thread-safety
>
>Does the -- enable-thread-safety need a value? I couldn't see anything
>to say that it does.
>
>  
>
No, it doesn't need a value.

>I'm assuming that I do not have to apply patch
>threadsafe-libpq-742.diff.gz as this is for PG7.4.2??
>
>  
>
It's conceivable that a new patch might be needed.  It's worth finding
out if it works now; you may be the "guinea pig" on it :-)

>I followed the instructions in the
>slony/doc/howto/slony-I-basic-mstr-slv.txt doc
>
>When I execute the following for both the master and slave nodes (by the
>way the nodes are the same machine - using IP address rather than
>localhost)
>
>intyonb01-postgres ># slon $CLUSTERNAME "dbname=$MASTERDBNAME
>user=$REPLICATIONUSER host=$MASTERHOST"
>
>I get the following:
>
>CONFIG main: slon version 1.0.5 starting up
>CONFIG main: local node id = 1
>CONFIG main: loading current cluster configuration
>CONFIG storeNode: no_id=2 no_comment='Slave node'
>CONFIG storePath: pa_server=2 pa_client=1
>pa_conninfo="dbname=pgbenchslave host=172.18.4.129 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='All pgbench 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_type,        ev_data1, ev_data2,
>ev_data3, ev_data4,        ev_data5, ev_data6,        ev_data7, ev_data8
>from "_slony_example".sl_event e where (e.ev_origin = '2' and e.ev_seqno
>  
>
>>'0') order by e.ev_origin, e.ev_seqno" - could not receive data from
>>    
>>
>server: Error 0
>
>intyonb01-postgres ># slon $CLUSTERNAME "dbname=$SLAVEDBNAME
>user=$REPLICATIONUSER host=$SLAVEHOST"
>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='Master Node'
>CONFIG storePath: pa_server=1 pa_client=2 pa_conninfo="dbname=pgbench
>host=172.18.4.129 user=postgres" pa_connretry=10
>CONFIG storeListen: li_origin=1 li_receiver=2 li_provider=1
>CONFIG storeSet: set_id=1 set_origin=1 set_comment='All pgbench 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
>ERROR  remoteListenThread_1: "select ev_origin, ev_seqno, ev_timestamp,
>ev_minxid, ev_maxxid, ev_xip,        ev_type,        ev_data1, ev_data2,
>ev_data3, ev_data4,        ev_data5, ev_data6,        ev_data7, ev_data8
>from "_slony_example".sl_event e where (e.ev_origin = '1' and e.ev_seqno
>  
>
>>'6') order by e.ev_origin, e.ev_seqno" - could not receive data from
>>    
>>
>server: Error 0
>
>
>Any help in resolving this issue would be much appreciated.
>
That is indeed the behaviour that has been typical when experiencing the
"threading issue".

I haven't looked at the patch lately; you might try applying the 7.4.2
patch to 8.0, and see how the sources vary.