Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ee5tM-0007AV-3k for pgsql-bugs@arkaria.postgresql.org; Tue, 23 Jan 2018 21:14:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ee5tL-0002xu-MQ for pgsql-bugs@arkaria.postgresql.org; Tue, 23 Jan 2018 21:14:03 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ee5tL-0002xk-DN for pgsql-bugs@lists.postgresql.org; Tue, 23 Jan 2018 21:14:03 +0000 Received: from forward4j.cmail.yandex.net ([2a02:6b8:0:1630::17]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ee5tH-00078h-Db for pgsql-bugs@lists.postgresql.org; Tue, 23 Jan 2018 21:14:02 +0000 Received: from mxback15g.mail.yandex.net (mxback15g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:94]) by forward4j.cmail.yandex.net (Yandex) with ESMTP id 1144A20FA2; Wed, 24 Jan 2018 00:13:53 +0300 (MSK) Received: from web54j.yandex.ru (web54j.yandex.ru [2a02:6b8:0:1619::34e]) by mxback15g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id b8fzVY4aoF-DpSqAxPv; Wed, 24 Jan 2018 00:13:52 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zsrv.org; s=mail; t=1516742032; bh=nlNEfzrRQWN0csKTrMW1PebX9XYQD7xRpq361dRCQHY=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date; b=F0xWEuu890xUzduKjmqcw6Z22Op58xDek38s3wOJA6PRWthyccyjbHhZLOEJ2+wzZ LLOekIS0IeKuJdWCYMyz+B2wdIdFWiqQVLFy0dTtbCOcsG/m4+hikejBdmQXMFd97B vWMUn3fl5W6YAJSJ2fgMkV1LvJOHrWHW7a12VTNo= Authentication-Results: mxback15g.mail.yandex.net; dkim=pass header.i=@zsrv.org Received: by web54j.yandex.ru with HTTP; Wed, 24 Jan 2018 00:13:51 +0300 From: Sergei Kornilov To: Kyotaro HORIGUCHI , "michael.paquier@gmail.com" Cc: "x4mmm@yandex-team.ru" , "david@nlpgo.com" , "pgsql-bugs@lists.postgresql.org" , "pgsql-hackers@postgresql.org" In-Reply-To: <20180118.211449.240575561.horiguchi.kyotaro@lab.ntt.co.jp> References: <20180118.144851.24081723.horiguchi.kyotaro@lab.ntt.co.jp> <62C2B9A0-51BC-40FF-9BCA-F203784CB9C1@yandex-team.ru> <20180118082505.GA84508@paquier.xyz> <20180118.211449.240575561.horiguchi.kyotaro@lab.ntt.co.jp> Subject: Re: Index-only scan returns incorrect results when using a composite GIST index with a gist_trgm_ops column. MIME-Version: 1.0 Message-Id: <348951516742031@web54j.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Wed, 24 Jan 2018 00:13:51 +0300 Content-Transfer-Encoding: 7bit Content-Type: text/plain List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello I tested this patch and think it can be commited to master. Is there a CF record? I can not find one. Should we also make backport to older versions? I test on REL_10_STABLE - patch builds and works ok, but "make check" fails on new testcase with error: > CREATE INDEX ON t USING gist (a test_inet_ops, a inet_ops); >+ ERROR: missing support function 4 for attribute 1 of index "t_a_a1_idx" and with different explain results. regards, Sergei