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 <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1gylFv-0008Gd-0i
	for pgsql-hackers@arkaria.postgresql.org; Tue, 26 Feb 2019 22:31:19 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1gylFt-0003js-Pk
	for pgsql-hackers@arkaria.postgresql.org; Tue, 26 Feb 2019 22:31:17 +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 <tgl@sss.pgh.pa.us>)
	id 1gylFt-0003dW-Ey
	for pgsql-hackers@lists.postgresql.org; Tue, 26 Feb 2019 22:31:17 +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 <tgl@sss.pgh.pa.us>)
	id 1gylFq-0000Lf-SW
	for pgsql-hackers@lists.postgresql.org; Tue, 26 Feb 2019 22:31:16 +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 x1QMVCCj015031;
	Tue, 26 Feb 2019 17:31:12 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Paul Ramsey <pramsey@cleverelephant.ca>
cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Allowing extensions to supply operator-/function-specific info
In-reply-to: <4CB71702-3E0F-4F81-AD50-12A8B4825239@cleverelephant.ca>
References: <15193.1548028093@sss.pgh.pa.us> <6953.1548297558@sss.pgh.pa.us>
 <6044.1548524131@sss.pgh.pa.us>
 <CA+TgmoYkLjVcbZZ8PYyaCTMYZJCQ8eiod8MSRMDaczjBw=a0bQ@mail.gmail.com>
 <19993.1548697885@sss.pgh.pa.us>
 <CACowWR3jZ4Xo1atU5xTDpEoeeKSw1==sKPhCy3a29HtcE9oQVQ@mail.gmail.com>
 <7671.1551135674@sss.pgh.pa.us>
 <CACowWR3_RyPSYO6a8TVLZ7KnL_rDNh2ywkSTeqFmrAPpP4y6-g@mail.gmail.com>
 <11051.1551139751@sss.pgh.pa.us>
 <CACowWR1ycbLx0t7WwT8uuJnK7E3U+tfzKXBRPaQrgHiCG+hvbA@mail.gmail.com>
 <14747.1551219541@sss.pgh.pa.us>
 <4CB71702-3E0F-4F81-AD50-12A8B4825239@cleverelephant.ca>
Comments: In-reply-to Paul Ramsey <pramsey@cleverelephant.ca>
	message dated "Tue, 26 Feb 2019 14:29:59 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <15029.1551220272.1@sss.pgh.pa.us>
Date: Tue, 26 Feb 2019 17:31:12 -0500
Message-ID: <15030.1551220272@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Precedence: bulk

Paul Ramsey <pramsey@cleverelephant.ca> writes:
> On Feb 26, 2019, at 2:19 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> What's the query look like exactly?  The other two calls will occur
>> anyway, but SupportRequestIndexCondition depends on the function
>> call's placement.

> select geos_intersects_new(g, 'POINT(0 0)') from foo;

Right, so that's not useful for an index scan.  Try

select * from foo where geos_intersects_new(g, 'POINT(0 0)').

			regards, tom lane