> On 8/7/06, Hannu Krosing <hannu at skype.net> wrote:
>> ?hel kenal p?eval, E, 2006-08-07 kell 10:31, kirjutas George Courter:
>> > I'm getting this error:
>> >
>> > ERROR:  duplicate key violates unique constraint
>> "sl_table_tab_reloid_key"
>> >
>> > when creating a second set. The first set is created/replicated fine.
>> > Then I try to create a second set containing some of the tables in the
>> > first set
>> No table is supposed to be in more than one set.
>>
> Ahah, thank you.
>
> So I will need multiple clusters to do what I want to do. Do you know
> what the performance impact is of having 5 clusters of well used
> tables(ie decent amount of inserts/replication) with each cluster
> having a set that contains tables that are in other clusters?

If you're trying to have a table in multiple replication sets, that won't
work, and having multiple clusters will merely muddy matters.

If you introduce a second cluster to try to get around this, what you'll
discover is that the triggers for the second cluster are liable to
eliminate those set up for the first cluster, thereby breaking the first
replication set.