Hi,
After a SUBSCRIBE_SET on a logshipping source node, the next sync
archive file contains the following innocuous stuff:
-- Slony-I log shipping archive
-- Node 1, Event 665
start transaction;
-- SUBSCRIBE_SET
------------------------------------------------------------------
-- End Of Archive Log
------------------------------------------------------------------
commit;
vacuum analyze "_oxrsorg".sl_setsync_offline;
The one after that, however, does this:
-- Slony-I log shipping archive
-- Node 1, Event 666
start transaction;
delete from "public"."test_table";copy "public"."test_table"
("id","dummy_field1","dummy_f
ield2","dummy_field3") from stdin;
\.
select "_cluster".finishTableAfterCopy(106); analyze "public"."test_table";
select "pg_catalog".setval('"public"."test_table"', '1');
insert into "_cluster".sl_setsync_offline (ssy_setid, ssy_seqno) values
('5', '272239904');
------------------------------------------------------------------
-- End Of Archive Log
------------------------------------------------------------------
commit;
vacuum analyze "_cluster".sl_setsync_offline;
Why does ssy_seqno get set to 272239904 for the new set?
This causes the application of subsequent syncs to fail.
Additionally, there remains the issue that there is no row in
_cluster.sl_setsync_offline
for the new sequence(s) in the new set
--
JP Fletcher
Database Administrator
Afilias Canada
voice: 416.646.3304 ext. 123
fax: 416.646.3305
mobile: 416.561.4763
[EMAIL PROTECTED]
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
