From: "n.pettik" <korablev@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v2 4/4] sql: remove OP_LoadPtr
Date: Tue, 10 Jul 2018 23:34:34 +0300 [thread overview]
Message-ID: <E70CED0D-075C-4EFB-8A93-6DA7F36E35F5@tarantool.org> (raw)
In-Reply-To: <e25ac786-bb45-a7e4-444b-d2b77b57d6df@tarantool.org>
> Yes, you are wrong here, because it was used to restore pointer to
> struct space "_index", but "_index" is a system space, and it is never
> altered. So pointer to "_index" is always valid, and it makes no sense
> to restore it on runtime.
Then I am OK with last patch in series.
next prev parent reply other threads:[~2018-07-10 20:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 17:08 [tarantool-patches] [PATCH v2 0/4] sql: get rid off sqlite3NestedParse Kirill Shcherbatov
2018-07-10 17:08 ` [tarantool-patches] [PATCH v2 1/4] sql: get rid off sqlite3NestedParse in clean stats Kirill Shcherbatov
2018-07-10 17:52 ` [tarantool-patches] " n.pettik
2018-07-11 7:22 ` Kirill Shcherbatov
2018-07-11 12:19 ` n.pettik
2018-07-11 12:23 ` Kirill Shcherbatov
2018-07-11 13:16 ` n.pettik
2018-07-10 17:08 ` [tarantool-patches] [PATCH v2 2/4] sql: remove usless sqlite3NestedParse function Kirill Shcherbatov
2018-07-10 18:22 ` [tarantool-patches] " n.pettik
2018-07-11 7:22 ` Kirill Shcherbatov
2018-07-10 17:08 ` [tarantool-patches] [PATCH v2 3/4] sql: refactor vdbe_emit_open_cursor calls Kirill Shcherbatov
2018-07-10 18:22 ` [tarantool-patches] " n.pettik
2018-07-11 7:22 ` Kirill Shcherbatov
2018-07-10 17:08 ` [tarantool-patches] [PATCH v2 4/4] sql: remove OP_LoadPtr Kirill Shcherbatov
2018-07-10 18:34 ` [tarantool-patches] " n.pettik
2018-07-10 20:23 ` Vladislav Shpilevoy
2018-07-10 20:34 ` n.pettik [this message]
2018-07-11 13:45 ` [tarantool-patches] Re: [PATCH v2 0/4] sql: get rid off sqlite3NestedParse 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=E70CED0D-075C-4EFB-8A93-6DA7F36E35F5@tarantool.org \
--to=korablev@tarantool.org \
--cc=tarantool-patches@freelists.org \
--cc=v.shpilevoy@tarantool.org \
--subject='[tarantool-patches] Re: [PATCH v2 4/4] sql: remove OP_LoadPtr' \
/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