Ibrahim Harrani ibrahim.harrani at gmail.com
Mon Jul 14 14:03:40 PDT 2008
Hi Chris,

I repaired the oid with REPAIR CONFIG on the master db(pg_dump was
issued on master)

I dropped the slave node with DROP NODE (ID =2);
But I can't UNINSTALL slave NODE  (UNINSTALL NODE (ID =2)

When I issue the commands (UNINSTALL NODE (ID =2) or the following sql
statements,
I always get "Table with id 54 not found"; But I believe that the
table is exist in the system and sl_table. What could be wrong in my
setup?

Thanks.

# SELECT _mycluster.uninstallNode();
Slony-I: alterTableRestore(): Table with id 54 not found
# SELECT _mycluster.setdroptable_int(54);
ERROR:  Slony-I: alterTableRestore(): Table with id 54 not found
# SELECT _mycluster.alterTableRestore(54);
ERROR:  Slony-I: alterTableRestore(): Table with id 54 not found

mydb=# SELECT * from _myusercluster.sl_table where tab_id=54;
 tab_id | tab_reloid | tab_relname | tab_nspname | tab_set |
tab_idxname  | tab_altered |       tab_comment
--------+------------+-------------+-------------+---------+--------------+-------------+-------------------------
     54 |     143265 | mytable   | myuser     |       2 | pk_mytable |
t           | Table myuser.mytable
(1 row)


mydb=# SELECT * from pg_catalog.pg_tables where tablename='mytable'
and tableowner='myuser';
 schemaname | tablename | tableowner | tablespace | hasindexes |
hasrules | hastriggers
------------+-----------+------------+------------+------------+----------+-------------
 myuser    | mytable | myuser    |            | t          | f        | t
(1 row)



On Mon, Jul 14, 2008 at 7:53 PM, chris <cbbrowne at ca.afilias.info> wrote:
> Glyn Astill <glynastill at yahoo.co.uk> writes:
>> AFAIK you cannot dump out, then restore a schema with slony in place.
>>
>> Slony uses object OIDs (as you've seen in alterTableRestore()) and even with the -o flag you cannot dump them, you can only dump the OIDs for row data, thus when you reload all your data the slony schema is junk.
>>
>> The only way to do it is to drop cascade the slony schema and setup the slony cluster again by starting from scratch or adding it as a new node to an existing cluster.
>>
>> Put me straight if I'm wrong here people.
>
> There is a Slonik command intended to do this sort of repair...
>  <http://linuxfinances.info/info/stmtrepairconfig.html>
> --
> select 'cbbrowne' || '@' || 'linuxfinances.info';
> http://cbbrowne.com/info/lsf.html
> Rules  of the  Evil Overlord  #145. "My  dungeon cell  decor  will not
> feature exposed pipes.  While they add to the  gloomy atmosphere, they
> are good  conductors of vibrations and  a lot of  prisoners know Morse
> code." <http://www.eviloverlord.com/>
>


More information about the Slony1-general mailing list