Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gMEzs-0001hC-AI for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Nov 2018 16:23:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gMExj-00019T-RS for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Nov 2018 16:21:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gMExj-00018W-GH for pgsql-hackers@lists.postgresql.org; Mon, 12 Nov 2018 16:21:19 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gMExh-0000b1-5u for pgsql-hackers@postgresql.org; Mon, 12 Nov 2018 16:21:18 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id wACGLAuF005157; Mon, 12 Nov 2018 11:21:10 -0500 From: Tom Lane To: Alexander Kuzmenkov cc: PostgreSQL-development Subject: Re: Uninterruptible long planning of a query with too many WHERE clauses In-reply-to: <37b95215-b315-ecbc-0747-037ac48ad4c4@postgrespro.ru> References: <90c5bdfa-d633-dabe-9889-3cf3e1acd443@postgrespro.ru> <21010.1541911093@sss.pgh.pa.us> <37b95215-b315-ecbc-0747-037ac48ad4c4@postgrespro.ru> Comments: In-reply-to Alexander Kuzmenkov message dated "Mon, 12 Nov 2018 15:05:28 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <5155.1542039670.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Mon, 12 Nov 2018 11:21:10 -0500 Message-ID: <5156.1542039670@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alexander Kuzmenkov writes: > El 11/11/18 a las 07:38, Tom Lane escribió: >> I think you have the right basic idea, but we don't have to completely >> lobotomize the bitmap-and search logic in order to cope with this. >> This code is only trying to figure out which paths are potentially >> redundant, so for a path with too many quals, we can just deem it >> not-redundant, as attached. > Thanks for the patch, looks good to me. Pushed, thanks for reviewing. regards, tom lane