From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f194.google.com (mail-lj1-f194.google.com [209.85.208.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 6FD9E46970E for ; Thu, 6 Feb 2020 17:29:37 +0300 (MSK) Received: by mail-lj1-f194.google.com with SMTP id x7so6347191ljc.1 for ; Thu, 06 Feb 2020 06:29:37 -0800 (PST) Date: Thu, 6 Feb 2020 17:29:34 +0300 From: Konstantin Osipov Message-ID: <20200206142934.GB3311@atlas> References: <1580929886.742787051@f138.i.mail.ru> <20200205191731.GB4292@atlas> <1580986257.247207517@f306.i.mail.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1580986257.247207517@f306.i.mail.ru> Subject: Re: [Tarantool-patches] [PATCH v3 2/2] memtx: allow quota overuse for truncation and deletion List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ilya Kosarev Cc: tarantool-patches@dev.tarantool.org, v.shpilevoy@tarantool.org * Ilya Kosarev [20/02/06 13:51]: > > Well, the problem here is that garbage collection won't work properly > in this case. I don't understand what GC has to do with it. Please clarify. > I guess it can be adjusted, however, there will be some > kind of crutches and it doesn't seem to be a good idea. Just switching > quota on and off seems to be more suitable and convenient for > truncations and deletions. >   -- Konstantin Osipov, Moscow, Russia