On 10/12/2004 3:30 PM, hannu at skype.net wrote:
>> On 10/12/2004 12:38 PM, hannu at skype.net wrote:
>>
>>> Currently I would be happy if I got some advice how to do it manually
>>
>> They are only supposed to live until every node has confirmed the SYNC
>> events that cover them. It all seems very much like one of the problems
>> we once had here on a test server, where dropping a node overlapped with
>> the slon process storing another "sl_confirm" row for it.
> 
> so DROP NODE is meant to clean these up ?
> 
> maybe there should be some functionality in RESET NODE, or slon startup 
> that removes sl_confirm entries without corresponding nodes in sl_node ?

 From CVS log:

> revision 1.29
> date: 2004/09/28 23:30:06;  author: wieck;  state: Exp;  lines: +13 -1
> Added code to the cleanup SP to remove confirm entries for
> non-existing nodes. There is a possible overlap when dropping
> a node and slon inserting confirm records. If this happened,
> log never got removed any more.
> 
> Also ignore confirms that are younger than 10 minutes. We had
> a case that is not entirely clear yet, but it looks as due to
> some server crash replication needed to be redone, but the
> provider had already deleted the event and log rows.
> 
> Jan

The latter is related to the "lost committed transactions" discussion, 
but still not confirmed.

It is backpatched into 1.0.3.


Jan


> 
> delete from sl_confirm
>  where con_origin not in (select no_id from sl_node where no_id=con_origin )
>     or con_received not in (select no_id from sl_node where
> no_id=con_received);
> 
> ----------------
> Hannu


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #