If that all checks out, be sure you aren't inadvertently putting rows in the base table.
On the provider node, do this: select count(*) from ONLY services.t_schema_objects_rastplaetze; If this is zero rows, then I suspect your data is all in the base table. Gordon Shannon wrote: > > Can you confirm that it's part of the replication set? On the subscriber > node, run this: > > select * from <your_slony_schema>.sl_table where > tab_relname='t_schema_objects_rastplaetze'; > > If that returns 0 rows, your table isn't part of a set. Next, confirm you > are subscribed to the set: > > select * from <your_slony_schema>.sl_subscribe; > > You should see sub_set=your set, sub_receiver=your subscriber node, and > sub_active=t. > > > > Josef Huber [EPCOM IT-Systeme] wrote: >> >> Hello, >> >> we are using Slony2.03 RC2 and Postgresql 8.4.0 and are Running under >> Suse SLES10 (SP2), i've 8 schema's, which i sync with slony, >> works fine on all normal Tables (are all synchron). >> >> I've 4 Tables which are inherited tables, and i get not all table >> synchron by slony, services.t_schema_objects_go is synchron, and >> services.t_schema_objects_rastplaetze is not synchron( 0 records on >> master 170 records) >> any idea? >> >> > > -- View this message in context: http://www.nabble.com/Slony-2.0.3RC2--Inherited-Table-tp25380708p25386909.html Sent from the Slony-I -- General mailing list archive at Nabble.com. _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
