From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp3.mail.ru (smtp3.mail.ru [94.100.179.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id C2D2446970E for ; Fri, 27 Dec 2019 14:31:32 +0300 (MSK) References: <4189b72ec3cd58478e899ac669b5aaaf4e1077a7.1577321174.git.korablev@tarantool.org> From: Vladislav Shpilevoy Message-ID: Date: Fri, 27 Dec 2019 14:31:31 +0300 MIME-Version: 1.0 In-Reply-To: <4189b72ec3cd58478e899ac669b5aaaf4e1077a7.1577321174.git.korablev@tarantool.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Tarantool-patches] [PATCH] sql: fix index consideration with INDEXED BY clause List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Nikita Pettik , tarantool-patches@dev.tarantool.org Hi! Thanks for the patch! LGTM. On 26/12/2019 01:48, Nikita Pettik wrote: > Accidentally, number of indexes to be considered during query planning > in presence of INDEXED BY is calculated wrong. Instead of one (INDEXED > BY is not a hint but requirement) index to be used (which is indicated > in INDEXED BY clause), all space indexes take part in query planning. > There are not so many tests checking this feature, so unfortunately this > bug was hidden. Let's fix it and force only one index to be used in QP > in case of INDEXED BY clause. > --- > Branch: https://github.com/tarantool/tarantool/tree/np/sql-indexed-by-fix