Wed Aug 3 21:04:43 PDT 2005
- Previous message: [Slony1-general] Improper Replication of structure
- Next message: [Slony1-general] Safe to delete from pg_namespace?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
We performed one large transactional update (2.3 million rows) on our master db yesterday that took roughly 15 minutes to execute. Seventeen hours later it still hasn't cleared through to the two slave subscribers. The status for one of the subscribers is: st_origin | 1 st_received | 3 st_last_event | 579105 st_last_event_ts | 2005-08-03 12:10:21.826932 st_last_received | 536291 st_last_received_ts | 2005-08-03 12:07:52.816493 st_last_received_event_ts | 2005-08-02 18:34:29.121862 st_lag_num_events | 42814 st_lag_time | 17:35:54.432473 After pouring over the literature I haven't been able to determine how I can figure out where this big update stands on the slaves by looking at the slony logs or sl_* tables. I'm trying to figure out whether it is stalled or how much has been processed. In short, I'm trying to figure out whether we should wait (its almost done) or just start over and resync the subscribers. Does anyone know how to figure this out? We are using Slony 1.0.5 with Postgres 7.4.6. Thanks ahead of time for any help. Christian
- Previous message: [Slony1-general] Improper Replication of structure
- Next message: [Slony1-general] Safe to delete from pg_namespace?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list