I'm seeing the following error in my logs and I don't quite understand 
why.  The sequence noted in the error is the 19th sequence in the set. 
It's the first set, so I don't know how it is possible that the 19th 
sequence id could already be used:

2008-06-10 16:09:01 EDT ERROR  remoteWorkerThread_1: "select 
"_ser_cluster".setAddSequence_int(1, 19, '"public"."sched_recid_seq"', 
'Sequence public.sched_recid_seq')" PGRES_FATAL_ERROR ERROR:  Slony-I: 
setAddSequence_int(): sequence ID 19 has already been assigned


Any insights will be greatly appreciated.  Here is the set definition:

  "avldsSet" => {

     "set_id" => 1,
     "table_id"    => 1,
     "sequence_id" => 1,

      "pkeyedtables" => [
         "avlds", "bill", "cash", "edi204h", "edi210h",
         "edi214h", "fax", "invoice", "item", "logs",
         "mbill", "mcash", "monetary", "move", "mpaid",
         "mpay", "pallet", "pay", "sched", "settle"
     ],

     "sequences" => [
         "avlds_recid_seq", "bill_recid_seq", "cash_recid_seq",
         "edi204h_recid_seq", "edi210h_recid_seq", "edi214h_recid_seq",
         "fax_recid_seq", "invoice_recid_seq", "item_recid_seq",
         "logs_recid_seq", "mbill_recid_seq", "mcash_recid_seq",
         "monetary_recid_seq", "move_recid_seq", "mpaid_recid_seq",
         "mpay_recid_seq", "pallet_recid_seq", "pay_recid_seq",
         "sched_recid_seq", "settle_recid_seq", "avlds_order_num_seq"
         ],
     },


-- 
Until later, Geoffrey

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