hi
i have two problems:
1) 2-3 months ago i'v try to merge 1500 sets (ech 11 tables) into one big
single. after 10 sets have metged, slony on slave database stoped worging.
child process of slony was all thie time killed by system SYGSENV. strace
showed that last system call is futex, no other clue, no other error. so i
thought that slony have limitation of elements in one set, and i'v created
couple of medium sets with no more than 1000 tables. but week ago i had to
unsubscribe set and subscribe it again, and again, slony child process was
terminated on and on by SIGSENV signal as he tryied subscribe set. any of
slony/postgres/system restart do not helped. but... i'v "manualy"
unsubscribed set (deleted emtries in sl_subscribe, sl_setsync,
sl_event...) and again started slony and slony stared to working
(synchronizing other sets). when synchronization was on the fly, a have
again subscribed set and this time operation finished. any clue what may
been happened ? if i again face this problem, what to check, where and how
?
2) i have two sets (s1 and s2) in slave database (sd1) replicated from
master (m1). tables in those sets are connected by foreign keys (across
sets). but schema/shape of database changed : there is another master
database (m2) which is origin of first set (s1) and for this set is
another slave database (sd2).
before:
------ s1 ------ >
m1
-------s2 ------->
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
