From: Nikita Tatunov <hollow653@gmail.com> To: Alexander Turenko <alexander.turenko@tarantool.org> Cc: tarantool-patches@freelists.org, korablev@tarantool.org Subject: [tarantool-patches] Re: [PATCH] sql: xfer optimization issue Date: Tue, 31 Jul 2018 20:04:32 +0300 [thread overview] Message-ID: <CAEi+_arTbtwK+qvS+jNgCF1YuhhazEHtYsrKhxrPZ+46jh52sQ@mail.gmail.com> (raw) In-Reply-To: <20180731132935.7tt5m23wntizv3vn@tkn_work_nb> Hello! Thanks for review, Diff is in the end! вт, 31 июл. 2018 г. в 16:29, Alexander Turenko <alexander.turenko@tarantool.org>: > > Hi! > > Thanks for updates. > > Answered inline. > > WBR, Alexander Turenko. > > > > > + /* > > > > + * Xfer optimization is unable to correctly insert data > > > > + * in case there's a conflict action other than > > > > + * explicit *_ABORT. This is the reason we want to only > > > > + * run it if the destination table is initially empty. > > > > + * That block generates code to make that determination. > > > > + */ > > > > + if (!(onError == ON_CONFLICT_ACTION_ABORT && > > > > + !is_err_action_default)) { > > > > > > Do you mean that: > > > > > > 1. The optimization non-empty table case correctly works only with ABORT > > > conflict action (default or explicit). > > > 2. The default conflict action can be overwritten on per-column basis, so > > > 'default abort' can really be replace or other conflict action. > > > > > > If so, your description doesn't give this information. > > > > > > To more on that, can we check per-column conflict actions instead of check > > > whether the conflict action default or explicit? This would enable more > > > cases > > > with non-empty tables for the optimization. And this would look less > > > confusing, > > > IMHO. > > > > > > > Well, basically, you're right. But the thing is that we're going to remove > > column conflict actions, thus, I suppose, it doesn't make sense. > > Nikita, Correct me if I'm wrong please. > > I recommend to comment such things in the code or commit message (as you > think it is more appropriate). It allows to decrease review iterations > at least :) I don't insist, though. > > > > I have one more question on that. It seems that SQLite has this > > > optimization > > > working with ROLLBACK conflict action. We cannot doing so, because of some > > > problem? Did this problem described / trackerized somewhere? Or something > > > changes underhood and makes this impossible? Are we know exact reason or > > > just > > > observing it does not work? > > > > > > > I investigated that a little. OP_IdxInsert was changed so that we can > > process > > ABORT, FAIL or IGNORE. I took it into account in newer version hence > > it is also used in these cases even when the destination table is not empty. > > So I understand it as follows: sqlite3's OP_IdxInsert just copy rows and > cannot handle non-trivial conflict actions, but tarantool's OP_IdxInsert > can handle it. However we have some non-investigated problems with > ROLLBACK and REPLACE as well as per-column conflict actions. > > I think that is is worth to investigate it a little deeper and file > issue(s), but this is not the blocker for this patch. > Yes, I'm on it. > > sqlite3VdbeAddOp2(v, OP_IdxInsert, iDest, regData); > > - sqlite3VdbeChangeP5(v, OPFLAG_NCHANGE); > > + switch (onError) { > > + case ON_CONFLICT_ACTION_IGNORE: > > + sqlite3VdbeChangeP5(v, OPFLAG_OE_IGNORE); > > + break; > > + case ON_CONFLICT_ACTION_FAIL: > > + sqlite3VdbeChangeP5(v, OPFLAG_OE_FAIL); > > + break; > > + default: > > + sqlite3VdbeChangeP5(v, OPFLAG_NCHANGE); > > + break; > > + } > > OPFLAG_NCHANGE is independent with other flags I think. > Fixed. > > +local function do_xfer_test(test, test_func, test_name, func, exp, opts) > > + local opts = opts or {} > > + local exp_xfer_count = opts.exp_xfer_count > > + local before = box.sql.debug().sql_xfer_count > > + local ok, result = pcall(test_func, test, test_name, func, exp) > > + local after = box.sql.debug().sql_xfer_count > > + if exp_xfer_count ~= nil then > > + ok = ok and test:is(after - before, exp_xfer_count, > > + test_name .. '-xfer-count') > > + end > > + return ok > > end > > I missed that do_execsql_test don't return a result and do_catchsql_test > returns {0} or {1}. So just don't same `ok` and `result` and remove > pcall. > Fixed. > By the way, we have 4 spaces indent for Lua accorsing to Lua Style > Guide. Fixed. diff --git a/src/box/sql/insert.c b/src/box/sql/insert.c index c3cf94a..041601c 100644 --- a/src/box/sql/insert.c +++ b/src/box/sql/insert.c @@ -1908,10 +1908,10 @@ xferOptimization(Parse * pParse, /* Parser context */ sqlite3VdbeAddOp2(v, OP_IdxInsert, iDest, regData); switch (onError) { case ON_CONFLICT_ACTION_IGNORE: - sqlite3VdbeChangeP5(v, OPFLAG_OE_IGNORE); + sqlite3VdbeChangeP5(v, OPFLAG_OE_IGNORE | OPFLAG_NCHANGE); break; case ON_CONFLICT_ACTION_FAIL: - sqlite3VdbeChangeP5(v, OPFLAG_OE_FAIL); + sqlite3VdbeChangeP5(v, OPFLAG_OE_FAIL | OPFLAG_NCHANGE); break; default: sqlite3VdbeChangeP5(v, OPFLAG_NCHANGE); diff --git a/test/sql-tap/gh-3307-xfer-optimization-issue.test.lua b/test/sql-tap/gh-3307-xfer-optimization-issue.test.lua index b99de2b..7778fce 100755 --- a/test/sql-tap/gh-3307-xfer-optimization-issue.test.lua +++ b/test/sql-tap/gh-3307-xfer-optimization-issue.test.lua @@ -6,14 +6,11 @@ local function do_xfer_test(test, test_func, test_name, func, exp, opts) local opts = opts or {} local exp_xfer_count = opts.exp_xfer_count local before = box.sql.debug().sql_xfer_count - local ok, result = pcall(test_func, test, test_name, func, exp) + test_func(test, test_name, func, exp) local after = box.sql.debug().sql_xfer_count - if exp_xfer_count ~= nil then - ok = ok and test:is(after - before, exp_xfer_count, + return test:is(after - before, exp_xfer_count, test_name .. '-xfer-count') end - return ok -end test.do_execsql_xfer_test = function(test, test_name, func, exp, opts) return do_xfer_test(test, test.do_execsql_test, test_name, func, exp, opts) diff --git a/test/sql-tap/with2.test.lua b/test/sql-tap/with2.test.lua index bd0187f..a59bac7 100755 --- a/test/sql-tap/with2.test.lua +++ b/test/sql-tap/with2.test.lua @@ -390,14 +390,11 @@ local function do_xfer_test(test, test_func, test_name, func, exp, opts) local opts = opts or {} local exp_xfer_count = opts.exp_xfer_count local before = box.sql.debug().sql_xfer_count - local ok, result = pcall(test_func, test, test_name, func, exp) + test_func(test, test_name, func, exp) local after = box.sql.debug().sql_xfer_count - if exp_xfer_count ~= nil then - ok = ok and test:is(after - before, exp_xfer_count, + return test:is(after - before, exp_xfer_count, test_name .. '-xfer-count') end - return ok -end test.do_execsql_xfer_test = function(test, test_name, func, exp, opts) return do_xfer_test(test, test.do_execsql_test, test_name, func, exp, opts)
next prev parent reply other threads:[~2018-07-31 17:04 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-18 15:32 [tarantool-patches] " N.Tatunov 2018-04-18 16:33 ` [tarantool-patches] " Hollow111 2018-04-19 11:22 ` n.pettik 2018-04-19 15:36 ` Hollow111 2018-04-20 1:02 ` n.pettik 2018-04-20 15:09 ` Hollow111 2018-04-20 16:09 ` n.pettik 2018-04-20 17:59 ` Hollow111 2018-04-23 23:40 ` n.pettik 2018-04-27 15:45 ` Hollow111 2018-05-03 22:57 ` n.pettik 2018-05-04 12:54 ` Hollow111 2018-06-28 10:18 ` Alexander Turenko 2018-07-09 15:50 ` Alexander Turenko 2018-07-16 12:54 ` Nikita Tatunov 2018-07-16 13:06 ` n.pettik 2018-07-16 13:20 ` Nikita Tatunov 2018-07-16 18:37 ` Nikita Tatunov 2018-07-16 19:12 ` n.pettik 2018-07-16 21:27 ` Nikita Tatunov 2018-07-18 15:13 ` n.pettik 2018-07-18 20:18 ` Nikita Tatunov 2018-07-19 0:20 ` n.pettik 2018-07-19 17:26 ` Nikita Tatunov 2018-07-20 3:20 ` n.pettik 2018-07-20 11:56 ` Nikita Tatunov 2018-07-20 16:43 ` n.pettik 2018-07-20 16:58 ` Nikita Tatunov 2018-07-29 1:12 ` Alexander Turenko 2018-07-29 11:23 ` n.pettik 2018-07-29 15:16 ` Alexander Turenko 2018-07-30 18:33 ` Nikita Tatunov 2018-07-30 22:17 ` Alexander Turenko 2018-07-31 11:48 ` Nikita Tatunov 2018-07-31 13:29 ` Alexander Turenko 2018-07-31 17:04 ` Nikita Tatunov [this message] 2018-07-31 17:44 ` Alexander Turenko 2018-08-21 16:43 ` 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=CAEi+_arTbtwK+qvS+jNgCF1YuhhazEHtYsrKhxrPZ+46jh52sQ@mail.gmail.com \ --to=hollow653@gmail.com \ --cc=alexander.turenko@tarantool.org \ --cc=korablev@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [PATCH] sql: xfer optimization issue' \ /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