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 1goVkl-0004II-Gf for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Jan 2019 15:56:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1goVkk-00069J-5K for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Jan 2019 15:56:46 +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 1goVkj-00068I-Qk for pgsql-hackers@lists.postgresql.org; Tue, 29 Jan 2019 15:56:45 +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 1goVkh-0006Z2-B9 for pgsql-hackers@lists.postgresql.org; Tue, 29 Jan 2019 15:56:44 +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 x0TFuevB029976; Tue, 29 Jan 2019 10:56:40 -0500 From: Tom Lane To: Simon Riggs cc: PostgreSQL Hackers Subject: Re: Allowing extensions to supply operator-/function-specific info In-reply-to: References: <15193.1548028093@sss.pgh.pa.us> <524.1548602263@sss.pgh.pa.us> <30311.1548741347@sss.pgh.pa.us> Comments: In-reply-to Simon Riggs message dated "Tue, 29 Jan 2019 06:12:02 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <29974.1548777400.1@sss.pgh.pa.us> Date: Tue, 29 Jan 2019 10:56:40 -0500 Message-ID: <29975.1548777400@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Simon Riggs writes: > On Tue, 29 Jan 2019 at 09:55, Tom Lane wrote: >> I have no particular >> interest in working on that right now, because it doesn't respond to >> what I understand PostGIS' need to be, and there are only so many >> hours in the day. But maybe it could be made workable in the future. > I thought the whole exercise was about adding generic tools for everybody > to use. Well, I'm building infrastructure plus a small subset of what might someday sit atop that infrastructure. I'm not prepared to commit right now to building stuff I can't finish for v12. > You said PostGIS was looking to > "automatically convert WHERE clauses into lossy index quals." which sounds > very similar to what I outlined. As I understand it, what they have is complex WHERE clauses from which they want to extract clauses usable with simple (non-expression) indexes. The case you seem to be worried about is the reverse: complicated index definition and simple WHERE clause. I think we're agreed that these two cases can't be solved with the very same facility. The support-function mechanism probably can be used to provide extensibility for logic that tries to attack the complicated-index case, but its mere existence won't cause that logic to spring into being. regards, tom lane