All,

We have an application that uses time partitioned tables (day-based).
We're in the early stages of implementing slony for database upgrades,
etc. I recently got the entire database up and synched, and it ran over
the weekend. We have a sliding window of time partitioned tables of 14
days. So, as of this morning the oldest three child tables were dropped
on the origin, and three new child tables have been created, also on the
origin. This morning I was going to manually unsubscribe the old child
tables, and run a slonik script to add/merge the new ones. However, I
noticed that on the receiver the parent table now has data in it, and
the dates range from Sep 9 - today. Normally it does not, the data is
only stored in the child tables which inherit from the parent. This
would make the range start 14 days from when I set up the replication,
last Friday. We replicate both the child tables and the parent. Can
anyone explain this behavior? Should I not be replicating the parent
table?

 

Doug Knight

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20080929/56982077/attachment.htm