RTFM, I figured it out.  The table id must be unique across sets, my 
bad.  The table id listed in the configuration file is the starting 
table id.

Geoffrey wrote:
> I posted about this once before, but didn't get any bites.  I'm hoping 
> someone can enlighten me as to my error here.  I have the following 
> configuration:
> 
> $SLONY_SETS = {
> 
>     "avldsSet" => {
>         "set_id"       => 1,
>             "table_id"     => 1,
>             "sequence_id"  => 1,
>             "pkeyedtables" => [....],
>         "keyedtables"  => {},
>             "serialtables" => [],
>             "sequences"    => [....],
>     }
> 
>     "nonavldsSet" => {
>         "set_id"       => 2,
>             "table_id"     => 2,
>             "sequence_id"  => 2,
>             "pkeyedtables" => [....],
>         "keyedtables"  => {},
>             "serialtables" => [],
>             "sequences"    => [....],
>     }
> };
> 
> When I attempt to create the second set, I get an error as follows:
> 
> slonik_create_set --config $CONFIG 2|slonik
> <stdin>:16: Subscription set 2 created
> <stdin>:17: Adding tables to the subscription set
> <stdin>:18: PGRES_FATAL_ERROR select "_mwv_cluster".setAddTable(2, 2, 
> 'public.aaccess', 'aaccess_pkey', 'Table public.aaccess with primary 
> key');  - ERROR:  Slony-I: setAddTable_int: table id 2 has already been 
> assigned!
> CONTEXT:  PL/pgSQL function "setaddtable" line 37 at perform
> 
> Clearly, 'table id 2' has not been already defined.  What is it that I'm 
> missing here?  Thanks for any assistance.
> 


-- 
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin