Hi there,

could someone advice me on the correct way of setting up a master -> 2 
slaves scenario? I'm doing the following:

Here's (part of the) replication setup script:

slonik <<_EOF_
cluster name = maildefender;
node 1 admin conninfo = 'dbname=test host=master user=pgsql';
node 2 admin conninfo = 'dbname=test host=slave1 user=pgsql';
node 3 admin conninfo = 'dbname=test host=slave2 user=pgsql';
init cluster (id=1, comment = 'Master Node');
create set (id=1, origin=1, comment='All testdb tables');
set add table (set id=1, origin=1, id=1, fully qualified name = 
'public.services', comment='services table');

[more tables added to set]

store node (id=2, comment = 'Slave node 1');
store path (server = 1, client = 2, conninfo='dbname=test host=master 
user=pgsql');
store path (server = 2, client = 1, conninfo='dbname=test host=slave1 
user=pgsql');
store listen (origin = 1, provider = 1, receiver = 2);
store listen (origin = 2, provider = 2, receiver =1);
store node (id=3, comment = 'Slave node 2');
store path (server = 1, client = 3, conninfo='dbname=test host=master 
user=pgsql');
store path (server = 3, client = 1, conninfo='dbname=test host=slave2 
user=pgsql');
store listen (origin = 1, provider = 1, receiver = 3);
store listen (origin = 3, provider = 3, receiver =1);
_EOF_

replication startup script:

slonik <<_EOF_
cluster name = maildefender;
node 1 admin conninfo = 'dbname=test host=master user=pgsql';
node 2 admin conninfo = 'dbname=test host=slave1 user=pgsql';
node 3 admin conninfo = 'dbname=test host=slave2 user=pgsql';
subscribe set ( id = 1, provider = 1, receiver = 2, forward = no);
subscribe set ( id = 1, provider = 1, receiver = 3, forward = no);
_EOF_

I then start the slon processes. One of the slaves refuses to start with 
the message:

ERROR  remoteWorkerThread_1: "begin transaction; set transaction 
isolation level serializable; lock table "_test".sl_config_lock; select 
"_test".enableSubscription(1, 1, 2); notify "_test_Event"; notify 
"_test_Confirm"; insert into "_test".sl_event     (ev_origin, ev_seqno, 
ev_timestamp,      ev_minxid, ev_maxxid, ev_xip, ev_type , ev_data1, 
ev_data2, ev_data3, ev_data4    ) values ('1', '62', '2004-11-02 
18:26:14.422032', '1431', '1432', '', 'ENABLE_SUBSCRIPTION', '1', '1', 
'2', 'f'); insert into "_test".sl_confirm   (con_origin, con_received, 
con_seqno, con_timestamp)    values (1, 3, '62', CURRENT_TIMESTAMP); 
commit transaction;" PGRES_FATAL_ERROR ERROR:  insert or update on table 
"sl_subscribe" violates foreign key constraint "sl_subscribe-sl_path-ref"
DETAIL:  Key (sub_provider,sub_receiver)=(1,2) is not present in table 
"sl_path".
INFO   remoteListenThread_1: disconnecting from 'dbname=test host=master 
user=pgsql'

I think that this means that the statement that should have populated 
the missing row in the 'sl_path' table would be:

store path (server = 1, client = 2, conninfo='dbname=test host=master 
user=pgsql');

Is that incorrectly expressed, or have I missed something else?

All three postgres installations can talk to eachother correctly.

Thanks in advance,

stefan

-- 
Dr Stefan Kruger <stefan at inty.net> http://www.inty.net
Developer, intY Ltd, 1700 Park Avenue, Aztec West,
Bristol BS32 4UA, UK. Telephone: +44 (0)1454 640500

The information contained in this e-mail message and any files
transmitted with it is confidential and may be legally privileged. It is
intended only for the addressee and others authorised to receive it. If
you are not the intended recipient or the person responsible for
delivering the message to the intended recipient you are advised that
you have received the e-mail in error and that any disclosure, copying,
distribution or action taken in reliance on the contents of the e-mail
and its attachments is strictly prohibited and may be unlawful. Please
advise the sender immediately if you are not the intended recipient.

Scanned for viruses by MailDefender