Hi,

We noticed that when we restart slony there's an event created on the 
local node (receiver) which is confirmed by others :

select * from _OURCLUSTER.sl_event where 
ev_origin=102;                                
 ev_origin | ev_seqno |        ev_timestamp        |     
ev_snapshot      | ev_type | ev_data1 | ev_data2 | ev_data3 | ev_data4 | 
ev_data5 | ev_data6 | ev_data7 | ev_data8
-----------+----------+----------------------------+----------------------+---------+----------+----------+----------+----------+----------+----------+----------+----------
       102 |       51 | 2010-05-20 12:27:00.099562 | 
338318875:338318875: | SYNC    |          |          |          
|          |          |          |          |
(1 row)

select * from _pns_slony_voila_archi_0.sl_confirm where con_origin=102;
 con_origin | con_received | con_seqno |       con_timestamp       
------------+--------------+-----------+----------------------------
        102 |          101 |        51 | 2010-05-20 12:27:02.78581
        102 |          103 |        51 | 2010-05-20 12:27:00.118815
        102 |          104 |        51 | 2010-05-20 12:27:00.253975
(3 rows)

However, this event row and the confirms rows are not deleted for a long 
time (>>30 mn). That's why test_slony_state.pl warns us about it. I know 
that we can modify the variables $WANTCONFIRM and $WANTAGE in this 
script, but I noticed that you use these SQL request in cleanupEvent 
function :

        delete from @NAMESPACE at .sl_confirm
                where con_origin = v_max_row.con_origin
                and con_received = v_max_row.con_received
                and con_seqno < v_max_row.con_seqno;

            delete from @NAMESPACE at .sl_event
                    where ev_origin = v_min_row.con_origin
                    and ev_seqno < v_max_sync;

The reason why our rows are not deleted is that the sequence value is 
the maximum value. I think you should use the operator <= instead of < 
to correct this behaviour.

What's your opinion ?
-- 
Cyril SCETBON