From: Konstantin Osipov <kostja@tarantool.org> To: tarantool-patches@freelists.org Subject: [tarantool-patches] Re: [PATCH 2/3] vinyl: move unique check optimization setup to the space level Date: Thu, 25 Jul 2019 01:31:41 +0300 [thread overview] Message-ID: <20190724223141.GB13150@atlas> (raw) In-Reply-To: <64b85c269c8153167e2aee302fecfab79ef58d43.1563895921.git.vdavydov.dev@gmail.com> * Vladimir Davydov <vdavydov.dev@gmail.com> [19/07/23 18:49]: > If any sub-set of fields indexed by a unique index is indexed by another > unique index, we can skip the uniqueness check for it. We use this to > optimize out unnecessary uniqueness checks in vinyl, where they may be > pretty costly, especially if the bloom filter doesn't reflect them. > > Currently, whether to check if an index is unique or not is determined > in vinyl space constructor, which sets vy_lsm::check_is_unique flag for > the space indexes. This looks ugly, because this means that no other > engine can make use of this optimization without duplicating the code > setting up the flags. True, no other engine needs it now, but still it > doesn't feel right. Besides, the check_is_unique flag isn't actually an > index property - it's rather a property of a space so storing it in > vy_lsm looks wrong. Because of that we have to update the flag when an > index is reassigned to another space by MoveIndex DDL operation, see > vinyl_space_swap_index(). > > So let's store the flags indicating whether a uniqueness check is > required for a particular index in a bitmap in the space struct and > set it up in the generic space constructor, space_create(). LGTM > +/** A trivial wrapper around space_build_index(). */ > +static void > +alter_space_build_index(struct space *src_space, struct space *new_space, > + struct index *new_index) > +{ > + bool check_unique = space_needs_check_unique(new_space, > + new_index->def->iid); check_unique is not proper English, please use check_unique_constraint or check_unique_ck. > + space_build_index_xc(src_space, new_index, new_space->format, > + check_unique); Why can't you move testing check_unique property inside space_build_index or even the engine specific implementation of space_build_index? > + space->unique_index_bitmap = calloc(bitmap_size(index_id_max + 1), 1); Let's use check_unique_constraint_map > +/** > + * Return true if the unique constraint must be checked for > + * the index with the given id before inserting a tuple into > + * the space. > + */ > +static inline bool > +space_needs_check_unique(struct space *space, uint32_t index_id) space_needs_unique_constraint_check -- Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2019-07-24 22:31 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-23 15:49 [PATCH 0/3] Fix crash on rollback of mixed DML/DDL transaction Vladimir Davydov 2019-07-23 15:49 ` [PATCH 1/3] vinyl: use update_def index method to update vy_lsm on ddl Vladimir Davydov 2019-07-24 22:25 ` [tarantool-patches] " Konstantin Osipov 2019-07-25 8:38 ` Vladimir Davydov 2019-07-25 12:11 ` Vladimir Davydov 2019-07-23 15:49 ` [PATCH 2/3] vinyl: move unique check optimization setup to the space level Vladimir Davydov 2019-07-24 22:31 ` Konstantin Osipov [this message] 2019-07-25 8:46 ` [tarantool-patches] " Vladimir Davydov 2019-07-25 12:11 ` Vladimir Davydov 2019-07-23 15:49 ` [PATCH 3/3] alter: fix rollback in case DDL and DML are used in the same transaction Vladimir Davydov 2019-07-24 22:32 ` [tarantool-patches] " Konstantin Osipov 2019-07-25 8:51 ` Vladimir Davydov 2019-07-30 10:56 ` Vladimir Davydov 2019-07-30 12:14 ` Konstantin Osipov
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=20190724223141.GB13150@atlas \ --to=kostja@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [PATCH 2/3] vinyl: move unique check optimization setup to the space level' \ /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