From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: Kirill Shcherbatov <kshcherbatov@tarantool.org>,
tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH v2 1/1] sql: use 64b bitmasks instead of 32b where possible
Date: Wed, 27 Mar 2019 14:46:57 +0300 [thread overview]
Message-ID: <772295c7-e691-05c4-ad72-ab3b8cb489e2@tarantool.org> (raw)
In-Reply-To: <84e81d55e8b11bc85fb9685df59548e2cc3feffb.1553085327.git.kshcherbatov@tarantool.org>
On 20/03/2019 15:36, Kirill Shcherbatov wrote:
> In some cases(like foreign keys) the SQL code used
> 32-bit bit mask, while 64-bit bit masks will perform better
> column optimizations. There was refactored code to work with 64b
> bitmasks where required.
> The 32b bitmasks are still used to specify constant OP_Function
> arguments because this change would require changing the P1 type
> of the VDBE p1 argument, which is not desirable. Moreover, the
> 64 function's arguments is an explicit overkill.
>
> The ticket was created in connection with the introduction of
> foreign keys and their use of 32-bit bit masks. In the rest of
> the scripts in SQL already use 64 bit masks, and the "smart" bit
> of the mask is not applicable.
>
> Closes #3571
>
> Branch: http://github.com/tarantool/tarantool/tree/kshch/gh-3571-sql-column-mask-64
> Issue: https://github.com/tarantool/tarantool/issues/3571
> ---
Please, put branch and issue links below that mark '---'. It
is not a cavil or 'red tape'. It really affects things. For example,
when somebody applies a patch from email, git can take these links
as a part of commit message.
LGTM.
next prev parent reply other threads:[~2019-03-27 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 12:36 [tarantool-patches] " Kirill Shcherbatov
2019-03-27 11:46 ` Vladislav Shpilevoy [this message]
2019-03-27 13:11 ` [tarantool-patches] " Kirill Yukhin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=772295c7-e691-05c4-ad72-ab3b8cb489e2@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=kshcherbatov@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH v2 1/1] sql: use 64b bitmasks instead of 32b where possible' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox