I'm not sure why repair config isn't working for you, however if you're looking for the baremetal function it is updatereloid(set, node).
----- Original Message ---- > From: Cyril Scetbon <[email protected]> > To: chris <[email protected]>; [email protected] > Sent: Tuesday, 11 August, 2009 10:48:18 > Subject: Re: [Slony1-general] Replacing PostgreSQL 8.2 by Pg 8.3 does not work > > Outch I can't dump the table oid (misunderstand between table oids and column > oids). I'll look at the slonik code for the repair command. > > Cyril Scetbon a écrit : > > you are right ! > > > > mydb=# select oid,relname from pg_class where relname = 't_512'; > > oid | relname > > -------+--------- > > 69187 | t_512 > > (1 row) > > > > mydb=# select * from _pns_slony_voila_preprod_1.sl_table where > tab_relname='t_512'; > > tab_id | tab_reloid | tab_relname | tab_nspname | tab_set | tab_idxname | > tab_altered | tab_comment > --------+------------+-------------+-------------+---------+-------------+-------------+------------------------------------- > > > > 512 | 24638 | t_512 | public | 1 | t_512_pkey | t > > > | Table public.t_512 with primary key > > (1 row) > > > > But, repair does not work correctly, and I can't debug it (tried by looking > > in > the postgresql query log, but found nothing) > > > > I'll try by dumping/reloading with oid. Any idea why the repair command > > does > not work correctly ? I don't see updates on the node I want to be repaired. I > used the following script : > > > > echo > /var/tmp/repair.sql > > slonik_print_preamble --config /etc/slony1/slon_tools_mydb.conf >> > /var/tmp/repair.sql > > for set in `seq 1 31` > > do > > echo "REPAIR CONFIG (SET ID = $set, EVENT NODE = 101, EXECUTE ONLY ON > > =103);" > >> /var/tmp/repair.sql > > done > > slonik < /var/tmp/repair.sql > > > > I got no error but nothing seems to be done > > > > thx > > > > chris a écrit : > >> Cyril Scetbon writes: > >> > >>> Alan Hodgson a écrit : > >>> > >>>> On Monday 10 August 2009, Cyril Scetbon > >>>> wrote: > >>>> > >>>>> However, when slony is started with pg 8.3 it does not see new events > >>>>> from his provider (still in pg8.3). > >>>>> If we restart our pg 8.2 with slony it works ! > >>>>> > >>>>> Do you know what we are missing ? > >>>>> > >>>>> thx > >>>>> > >>>> You need to modify all the table and sequence OIDs stored in the > >>>> slony configuration tables to reflect the new table and sequence > >>>> OIDs. > >>>> > >>> I don't think oids are used and table id were not modified > >>> > >> > >> No, Alan's quite right. > >> > >> If you look at sl_table and sl_sequence, you'll find "reloid" columns, > >> which are indeed relevant. > >> > >> > >>>> You need to update the slony functions through the appropriate slon > >>>> commands. > >>>> > >>> really ? > >>> > >> > >> The slonik "repair config" command should be useful. > >> > >> > >> > >> "Resets the name-to-oid mapping of tables in a replication set, useful > >> for restoring a node after a pg_dump." > >> > > > > -- Cyril SCETBON > _______________________________________________ > Slony1-general mailing list > [email protected] > http://lists.slony.info/mailman/listinfo/slony1-general _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
