Fri Sep 2 13:53:17 PDT 2011
- Previous message: [Slony1-general] trying to use pg_upgrade for 8.3 database with Slony 2.0.7
- Next message: [Slony1-general] pg_dump and replication lag in 2.0.7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Just to complete this thread -- I tried the method I outlined in my previous email on a test cluster where I ran the following script on the node before I ran pg_upgrade: > 1) stop slony; > 2) alter table sl_table alter column tab_relname type text, alter column tab_nspname type text, alter column tab_idxname type text; > alter table sl_sequence alter column seq_relname type text, alter column seq_nspname type text; > drop type vactables cascade; > CREATE TYPE vactables AS ( > nspname text, > relname text > ); > create function tablestovacuum () … leaving out function body… > > 3) pg_upgrade > > 4) start 9.0, do vacuuming analyze, etc… > > 5) fix slony back: > > alter table sl_table alter column tab_relname type name, alter column tab_nspname type name, alter column tab_idxname type name; > alter table sl_sequence alter column seq_relname type name, alter column seq_nspname type name; > drop type vactables cascade; > CREATE TYPE vactables AS ( > nspname name, > relname name > ); > create function tablestovacuum () … leaving out function body… > > 6) then start slony -- and it failed -- in an interesting way -- the node replicated one insert statement; and after that swallowed all replication events silently. For the moment, I'm going to have to upgrade the node when I can stop all write activities to the master node. I'll drop the node out of the slony set before I run pg_upgrade; upgrade it to 9.0 and then resubscribe it to the slony set using the omit copy flag. I've tested this now on a test cluster; and this works. -- ###################################################################### This email is confidential, does not constitute investment advice, is only for the use of the intended recipient and should not be redistributed, except with the sender's consent. If you received this email in error, please notify us immediately by telephone; receipt by anyone other than the intended recipient is not a waiver of any work-product or attorney-client privilege. All email to and from Millburn Ridgefield Corporation, The Millburn Corporation, Millburn International and any affiliates is monitored, stored and made available to regulators if requested. ######################################################################
- Previous message: [Slony1-general] trying to use pg_upgrade for 8.3 database with Slony 2.0.7
- Next message: [Slony1-general] pg_dump and replication lag in 2.0.7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list