Set up Slony on Windows - Mailing list pgadmin-support

I have pgAdmin III 1.6 Beta 3 on Windows XP with Slony 1.2 RC5 and
PostgreSQL 8.1.4.

Does anybopdy know if this combination should work?

I try to create a New Slony-I cluster and the script bombs out after
creating sl_registry:-

2006-10-20 15:53:31 NOTICE:  type "_ab.xxid" is not yet defined
2006-10-20 15:53:31 DETAIL:  Creating a shell type definition.
2006-10-20 15:53:31 NOTICE:  argument type _ab.xxid is only a shell
2006-10-20 15:53:31 NOTICE:  type "_ab.xxid_snapshot" is not yet
defined
2006-10-20 15:53:31 DETAIL:  Creating a shell type definition.
2006-10-20 15:53:31 NOTICE:  argument type _ab.xxid_snapshot is only a
shell
2006-10-20 15:53:31 NOTICE:  CREATE TABLE / PRIMARY KEY will create
implicit index "sl_node-pkey" for table "sl_node"
2006-10-20 15:53:31 NOTICE:  CREATE TABLE will create implicit sequence
"sl_nodelock_nl_conncnt_seq" for serial column "sl_nodelock.nl_conncnt"
2006-10-20 15:53:31 NOTICE:  CREATE TABLE / PRIMARY KEY will create
implicit index "sl_nodelock-pkey" for table "sl_nodelock"
2006-10-20 15:53:32 NOTICE:  CREATE TABLE / PRIMARY KEY will create
implicit index "sl_set-pkey" for table "sl_set"
2006-10-20 15:53:32 NOTICE:  CREATE TABLE / PRIMARY KEY will create
implicit index "sl_setsync-pkey" for table "sl_setsync"
2006-10-20 15:53:32 NOTICE:  CREATE TABLE / PRIMARY KEY will create
implicit index "sl_table-pkey" for table "sl_table"
2006-10-20 15:53:32 NOTICE:  CREATE TABLE / UNIQUE will create implicit
index "sl_table_tab_reloid_key" for table "sl_table"
2006-10-20 15:53:32 NOTICE:  CREATE TABLE / PRIMARY KEY will create
implicit index "sl_trigger-pkey" for table "sl_trigger"
2006-10-20 15:53:32 NOTICE:  CREATE TABLE / PRIMARY KEY will create
implicit index "sl_sequence-pkey" for table "sl_sequence"
2006-10-20 15:53:32 NOTICE:  CREATE TABLE / UNIQUE will create implicit
index "sl_sequence_seq_reloid_key" for table "sl_sequence"
2006-10-20 15:53:32 NOTICE:  CREATE TABLE / PRIMARY KEY will create
implicit index "sl_path-pkey" for table "sl_path"
2006-10-20 15:53:32 NOTICE:  CREATE TABLE / PRIMARY KEY will create
implicit index "sl_listen-pkey" for table "sl_listen"
2006-10-20 15:53:32 NOTICE:  CREATE TABLE / PRIMARY KEY will create
implicit index "sl_subscribe-pkey" for table "sl_subscribe"
2006-10-20 15:53:32 NOTICE:  CREATE TABLE / PRIMARY KEY will create
implicit index "sl_event-pkey" for table "sl_event"
2006-10-20 15:53:33 NOTICE:  CREATE TABLE / PRIMARY KEY will create
implicit index "sl_registry_pkey" for table "sl_registry"
2006-10-20 15:53:33 LOG:  server process (PID 3336) was terminated by
signal 5
2006-10-20 15:53:33 LOG:  terminating any other active server processes
2006-10-20 15:53:33 WARNING:  terminating connection because of crash
of another server process
2006-10-20 15:53:33 DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2006-10-20 15:53:33 HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2006-10-20 15:53:33 LOG:  all server processes terminated;
reinitializing
2006-10-20 15:53:33 LOG:  database system was interrupted at 2006-10-20
15:49:35 GMT Standard Time
2006-10-20 15:53:33 LOG:  checkpoint record is at 3/E00F5910
2006-10-20 15:53:33 LOG:  redo record is at 3/E00F5910; undo record is
at 0/0; shutdown TRUE
2006-10-20 15:53:33 LOG:  next transaction ID: 4217740; next OID: 87001
2006-10-20 15:53:33 LOG:  next MultiXactId: 1; next MultiXactOffset: 0
2006-10-20 15:53:33 LOG:  database system was not properly shut down;
automatic recovery in progress
2006-10-20 15:53:33 LOG:  redo starts at 3/E00F5958
2006-10-20 15:53:33 LOG:  unexpected pageaddr 3/CC27C000 in log file 3,
segment 224, offset 2605056
2006-10-20 15:53:33 LOG:  redo done at 3/E027BEB0
2006-10-20 15:53:36 LOG:  database system is ready
2006-10-20 15:53:36 LOG:  transaction ID wrap limit is 1077638593,
limited by database "prism"
2006-10-20 15:54:24 LOG:  autovacuum: processing database "postgres"