Tue Aug 8 08:04:32 PDT 2006
- Previous message: [Slony1-general] Problem with slony
- Next message: [Slony1-general] Slony-I+Partitioned tables
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
M?llner wrote: > > Hello! > > > > > > > > I need somethings, but i'm unable to solve my problems. Maybe you are > able to help me. > > > > I need queries to get the current state of the master (e.g. how many > lines have not been updated in the slaves). > > How do i manage this? > > > There is no particularly direct way of determining this. The cost of counting this would be pretty high... There is a built-in "status" view, sl_status, which gives various information about how far replication is behind on each subscriber node. The results of that view are only interesting when drawn from an origin node; you may want to check whether that may be satisfactory for monitoring system status. In version 1.2, information as to numbers of inserts/deletes/updates are recorded in the logs, but this is handled in a retrospective fashion, after the updates have been applied to a subscriber, as opposed to listing this information prospectively. I don't know if that will help solve your problem.
- Previous message: [Slony1-general] Problem with slony
- Next message: [Slony1-general] Slony-I+Partitioned tables
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list