Hi there -- new to this game.

I am faced with having to replicate a db from a RH6.0 box to a FreeBSD 
4.9 box. Latest stable release of postgres and slony.

I run into an error where there appears to be hard coded paths that 
assume that postgres and/or slony is always installed in the same place 
on master and slave:

[master] ~/syncdb]$ ./repl_setup
NOTICE:  type "_mydatabase.xxid" is not yet defined
DETAIL:  Creating a shell type definition.
NOTICE:  argument type _mydatabase.xxid is only a shell
NOTICE:  type "_mydatabase.xxid_snapshot" is not yet defined
DETAIL:  Creating a shell type definition.
NOTICE:  argument type _mydatabase.xxid_snapshot is only a shell
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index 
"sl_node-pkey" for table "sl_node"
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index 
"sl_set-pkey" for table "sl_set"
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index 
"sl_setsync-pkey" for table "sl_setsync"
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index 
"sl_table-pkey" for table "sl_table"
NOTICE:  CREATE TABLE / UNIQUE will create implicit index 
"sl_table_tab_reloid_key" for table "sl_table"
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index 
"sl_trigger-pkey" for table "sl_trigger"
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index 
"sl_sequence-pkey" for table "sl_sequence"
NOTICE:  CREATE TABLE / UNIQUE will create implicit index 
"sl_sequence_seq_reloid_key" for table "sl_sequence"
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index 
"sl_path-pkey" for table "sl_path"
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index 
"sl_listen-pkey" for table "sl_listen"
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index 
"sl_subscribe-pkey" for table "sl_subscribe"
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index 
"sl_event-pkey" for table "sl_event"
<stdin>:55: loading of file /usr/local/pgsql/share/slony1_funcs.sql: 
PGRES_FATAL_ERROR ERROR:  current transaction is aborted, commands 
ignored until end of transaction block
ERROR:  current transaction is aborted, commands ignored until end of 
transaction block

The repl_setup script:
#!/bin/sh
slonik <<_EOF_
cluster name = mydatabase;
node 1 admin conninfo = 'dbname=mydatabase host=linux.mydomain.com 
user=postgres';
node 2 admin conninfo = 'dbname=mydatabase host=freebsd.mydomain.com 
user=pgsql';
init cluster (id=1, comment = 'Master Node');
create set (id=1, origin=1, comment='All tables');
set add table (set id=1, origin=1, id=1, fully qualified name = 
'public.services', comment='services table');

# more tables added to set here, removed for brevity

store node (id=2, comment = 'Slave node');
store path (server = 1, client = 2, conninfo='dbname=mydatabase 
host=linux.mydomain.com user=postgres');
store path (server = 2, client = 1, conninfo='dbname=mydatabase 
host=freebsd.mydomain.com user=pgsql');
store listen (origin = 1, provider = 1, receiver = 2);
store listen (origin = 2, provider = 2, receiver = 1);
_EOF_

The file /usr/local/pgsql/share/slony1_funcs.sql sits in a different 
place on the slave, namely /usr/local/share/postgresql/slony1_funcs.sql.

I tried making /usr/local/pgsql/share a symlink to 
/usr/local/share/postgresql, but that made no difference.

I am probably missing something blatantly obvious here. I would 
appreciate if someone could offer any pointers to what I've bodged.

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