Vivek Khera wrote:
> 
> On Feb 20, 2008, at 9:09 AM, Geoffrey wrote:
> 
>> "tract_order_num_key" unique, btree (order_num)
>>
>> So, this application has been running along just fine like this for a 
>> couple of years.  Is it possible that the above index is causing the 
>> problem?
> 
> slony won't care about this index.  all it cares is that you have a 
> primary key defined for the table.  your above key does not qualify as a 
> primary key.

Understood.  We do have a primary key on this index:

Indexes:
     "tract_pkey" primary key, btree (recid)
     "tract_order_num_key" unique, btree (order_num)
     "tract_assigned" btree (assigned)
     "tract_code" btree (code)
     "tract_comments" btree (comments)
     "tract_compound_1" btree (code, old_order_num)
     "tract_date_avail" btree (date_avail)
     "tract_dest_state" btree (dest_state)
     "tract_dest_zone" btree (dest_zone)
     "tract_driver" btree (driver)
     "tract_orig_state" btree (orig_state)
     "tract_orig_zone" btree (orig_zone)
     "tract_prebooked" btree (prebooked)
     "tract_tractor_num" btree (tractor_num)
     "tract_trailer_num" btree (trailer_num)

-- 
Until later, Geoffrey

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