Mon Mar 29 16:24:03 PDT 2010
- Previous message: [Slony1-general] Slony 2.0.2 and PostgreSQL 8.4: initial copy fails (Could not lock table on subscriber)
- Next message: [Slony1-general] PostgreSQL 8.4 support in Slony 2.0.2?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Fixed - initial copy is going now. I dropped one of the tables from the initial synchronization slonik script, as the schema had diverged between master and slave. Thanks, Aleksey On Mon, Mar 29, 2010 at 3:41 PM, Aleksey Tsalolikhin <atsaloli.tech at gmail.com> wrote: > check_slony_cluster.sh reports: OK - 0 nodes in sync > > > test_slony_state-db.pl reports: > > > Tests for node 1 - DSN = dbi:Pg:dbname=ddcKeyGen host=MASTERIP user=postgres > ======================================== > pg_listener info: > Pages: 0 > Tuples: 0 > > Size Tests > ================================================ > sl_log_1 8 212.000000 > sl_log_2 117 3133.000000 > sl_seqlog 0 0.000000 > > Listen Path Analysis > =================================================== > No problems found with sl_listen > > -------------------------------------------------------------------------------- > Summary of event info > Origin Min SYNC Max SYNC Min SYNC Age Max SYNC Age > ================================================================================ > 1 96 1987 00:00:00 03:47:00 0 > 2 3 3 03:47:00 03:47:00 1 > > > --------------------------------------------------------------------------------- > Summary of sl_confirm aging > Origin Receiver Min SYNC Max SYNC Age of latest SYNC Age of > eldest SYNC > ================================================================================= > 1 2 97 97 03:46:00 03:46:00 1 > 2 1 3 3 03:47:00 03:47:00 1 > > > ------------------------------------------------------------------------------ > > Listing of old open connections on node 1 > Database PID User Query Age > Query > ================================================================================ > > > Tests for node 2 - DSN = dbi:Pg:dbname=ddcKeyGen_slave host=SLAVEIP > user=postgres > ======================================== > pg_listener info: > Pages: 0 > Tuples: 0 > > Size Tests > ================================================ > sl_log_1 0 0.000000 > sl_log_2 0 0.000000 > sl_seqlog 0 0.000000 > > Listen Path Analysis > =================================================== > No problems found with sl_listen > > -------------------------------------------------------------------------------- > Summary of event info > Origin Min SYNC Max SYNC Min SYNC Age Max SYNC Age > ================================================================================ > 1 96 97 03:47:00 03:47:00 1 > 2 3 3 03:48:00 03:48:00 1 > > > --------------------------------------------------------------------------------- > Summary of sl_confirm aging > Origin Receiver Min SYNC Max SYNC Age of latest SYNC Age of > eldest SYNC > ================================================================================= > 1 2 97 97 03:47:00 03:47:00 1 > 2 1 3 3 03:48:00 03:48:00 1 > > > ------------------------------------------------------------------------------ > > Listing of old open connections on node 2 > Database PID User Query Age > Query > ================================================================================ > > > What do I do to get the initial copy working? > > Thanks, > -at >
- Previous message: [Slony1-general] Slony 2.0.2 and PostgreSQL 8.4: initial copy fails (Could not lock table on subscriber)
- Next message: [Slony1-general] PostgreSQL 8.4 support in Slony 2.0.2?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list