Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jL7Yw-0002uM-7e for pgsql-hackers@arkaria.postgresql.org; Sun, 05 Apr 2020 15:51:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jL7Yv-0007Yg-3m for pgsql-hackers@arkaria.postgresql.org; Sun, 05 Apr 2020 15:51:53 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jL7Yu-0007YM-Sx for pgsql-hackers@lists.postgresql.org; Sun, 05 Apr 2020 15:51:52 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jL7Ys-0001EF-PR for pgsql-hackers@postgresql.org; Sun, 05 Apr 2020 15:51:51 +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 035FpfUf012094; Sun, 5 Apr 2020 11:51:41 -0400 From: Tom Lane To: Alexander Korotkov cc: Tomas Vondra , Michael Paquier , Alvaro Herrera , Andres Freund , Mark Dilger , pgsql-hackers Subject: Re: WIP: BRIN multi-range indexes In-reply-to: References: <20190914173049.welhipsj7bijqahm@development> <20190925200748.GA22809@alvherre.pgsql> <20190926190148.piwdqnfc2brargqq@development> <20191201015502.GF2355@paquier.xyz> <20200402022904.xssjyfupdaj2ejyp@development> Comments: In-reply-to Alexander Korotkov message dated "Sun, 05 Apr 2020 18:29:15 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12092.1586101901.1@sss.pgh.pa.us> Date: Sun, 05 Apr 2020 11:51:41 -0400 Message-ID: <12093.1586101901@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alexander Korotkov writes: > I'd like to give this patchset a chance for v13. I'm going to make > another pass trough this patchset. If I wouldn't find serious issues, > I'm going to commit it. Any objections? I think it is way too late to be reviving major features that nobody has been looking at for months, that indeed were never even listed in the final CF. At this point in the cycle I think we should just be trying to get small stuff over the line, not shove in major patches and figure they can be stabilized later. In this particular case, the last serious work on the patchset seems to have been Tomas' revision of 2019-09-14, and he specifically stated then that the APIs still needed work. That doesn't sound like "it's about ready to commit" to me. regards, tom lane