Sat Jan 12 17:00:42 PST 2008
- Previous message: [Slony1-general] Slony events in windows
- Next message: [Slony1-general] URGENT: Migration of master node locked my database
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Help please! I tried to migrate the Slony master node to a new server with this script. It seemed simple but... slonik <<_EOF_ cluster name = db_cluster; node 1 admin conninfo = 'dbname=db host=host1 user=postgres'; node 2 admin conninfo = 'dbname=db host=host2 user=postgres'; lock set (id = 1, origin = 1); wait for event (origin = 1, confirmed = 2); move set (id = 1, old origin = 1, new origin = 2); _EOF_ The script sat there for about 30 minutes with no activity. No CPU load, vmstat didn't show any activity, nothing, so I finally had to kill it. Now all of my tables are locked, and I can't do our weekend update of our data. When I try to do anything, I get: execute failed: ERROR: Slony-I: Table sample is currently locked against updates because of MOVE_SET operation in progress. Help! This is critical. I need to at least get back to where I can update our database, like TONIGHT! I thought this would be a fast operation, because in the past (on smaller databases), it's been virtually instantaneous. 1. How do I release the lock? 2. Why didn't the migration work??? Thanks! Craig
- Previous message: [Slony1-general] Slony events in windows
- Next message: [Slony1-general] URGENT: Migration of master node locked my database
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list