From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp40.i.mail.ru (smtp40.i.mail.ru [94.100.177.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id D9E4D445321 for ; Thu, 16 Jul 2020 03:05:28 +0300 (MSK) References: <1594821336-14468-1-git-send-email-alyapunov@tarantool.org> <1594821336-14468-5-git-send-email-alyapunov@tarantool.org> From: Vladislav Shpilevoy Message-ID: Date: Thu, 16 Jul 2020 02:05:27 +0200 MIME-Version: 1.0 In-Reply-To: <1594821336-14468-5-git-send-email-alyapunov@tarantool.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Tarantool-patches] [PATCH v3 04/13] txm: introduce dirty tuples List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Aleksandr Lyapunov , tarantool-patches@dev.tarantool.org Thanks for the patch! > diff --git a/src/box/tuple.h b/src/box/tuple.h > index 9a88772..4752323 100644 > --- a/src/box/tuple.h > +++ b/src/box/tuple.h > @@ -1081,8 +1087,10 @@ tuple_unref(struct tuple *tuple) > assert(tuple->refs - 1 >= 0); > if (unlikely(tuple->is_bigref)) > tuple_unref_slow(tuple); > - else if (--tuple->refs == 0) > + else if (--tuple->refs == 0) { > + assert(!tuple->is_dirty); My question regarding this assertion remains - who is supposed to remove the flag and when?