From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Allowing extensions to supply operator-/function-specific info
Date: Tue, 29 Jan 2019 10:56:40 -0500
Message-ID: <29975.1548777400@sss.pgh.pa.us> (raw)
In-Reply-To: <CANP8+jLFi1eccVESpW4zxdaFyWbrsn7cgu1UEtvbESggNVsXtg@mail.gmail.com>
References: <15193.1548028093@sss.pgh.pa.us>
<CANP8+jJ+TX2zc7hz_57BM0q+9JeZ-NE12iNyWLVAnT+JWSgNQQ@mail.gmail.com>
<524.1548602263@sss.pgh.pa.us>
<CANP8+jLMj6xwZ_1kBXD_CAfMKPo1Hvo=HvEgqbg+va6k5DGoCQ@mail.gmail.com>
<30311.1548741347@sss.pgh.pa.us>
<CANP8+jLFi1eccVESpW4zxdaFyWbrsn7cgu1UEtvbESggNVsXtg@mail.gmail.com>
Simon Riggs <simon@2ndquadrant.com> writes:
> On Tue, 29 Jan 2019 at 09:55, Tom Lane <tgl@sss.pgh.pa.us> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, simon@2ndquadrant.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Allowing extensions to supply operator-/function-specific info
In-Reply-To: <29975.1548777400@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox