<HTML><BODY><p style='margin-top: 0px;' dir="ltr">Hi!</p>
<p dir="ltr">Thanks for your comments.</p>
<p dir="ltr">When performing space: truncate(), we are executing<br>
simple upsert. How can we distinguish it from any other upsert to use reserved extents tech?</p>
пятница, 31 января 2020г., 11:21 +03:00 от Konstantin Osipov <a href="mailto:kostja.osipov@gmail.com">kostja.osipov@gmail.com</a>:<br><br><blockquote id="mail-app-auto-quote" cite="15804588921414045727" style="border-left:1px solid #005FF9; margin:0px 0px 0px 10px; padding:0px 0px 0px 10px;">
<div class="js-helper js-readmsg-msg">
<style type="text/css"></style>
<div >
<base target="_self" href="https://e.mail.ru/" />
<div id="style_15804588921414045727_BODY">* Ilya Kosarev <<a href="mailto:i.kosarev@tarantool.org">i.kosarev@tarantool.org</a>> [20/01/20 21:18]:<br>
<div class="mail-quote-collapse">> Trying to perform space:truncate() and space:delete() while reaching<br>
> memtx_memory limit we could experience slab allocator failure. This<br>
> behavior seems to be quite surprising for users. Now we are allowing<br>
> to overuse memtx quota if needed for truncation or deletion, using flag<br>
> in struct quota. After performing truncation or deletion we reset the<br>
> flag so that quota can be overused any more.<br>
</div><br>
This is duplicating the tech already existing with reserved<br>
extents.<br>
<br>
Why not use the reserved extents instead? Why do you need to turn<br>
quota completely on/off?<br>
<br>
<br>
-- <br>
Konstantin Osipov, Moscow, Russia<br>
</div>
<base target="_self" href="https://e.mail.ru/" />
</div>
</div>
</blockquote></BODY></HTML>