Carlos Gaona U. wrote:

>I'm trying to replicate two databases using (partially) the following to
>set up slony:
>
>...
># Set 1, for schema alpha
>create set (id=1, origin=1, comment='Alpha');
>set add table (set id=1, origin=1, id=1, fully qualified name =
>'alpha.category', comment='');
>....
># Set 2, for schema beta
>create set (id=1, origin=1, comment='Beta');
>set add table (set id=1, origin=1, id=1, fully qualified name =
>'beta.category', comment='');
>....
># Set 3, for schema gamma
>create set (id=1, origin=1, comment='Gamma');
>set add table (set id=1, origin=1, id=1, fully qualified name =
>'gamma.category', comment='');
>....
>
>alpha.category_pkey
>beta.category_pkey
>gamma.category_pkey
>
>So, i'm guessing that slony has a UNIQUE constraint on indexes names,
>and they are not stored with their fully qualified names (that is,
>including the schema they belong to) within the sl_table-pkey. I'm a
>right?
>  
>
No, Slony-I has no constraint on indexes names.

The problem you're running into is that you are trying to create
multiple tables with the same Slony-I table ID.

set add table (id = 1...
set add table (id = 1...
set add table (id = 1...

The ID value must be unique.

The fact that there are multiple sets does not make uniqueness
unnecessary, as you are permitted to move tables from one set to
another, using SET MOVE TABLE.

Make sure the table ID numbers are unique and you'll get past this issue.