| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add missing operator <->(box, point) |
| Date: | 2019-07-02 19:13:30 |
| Message-ID: | 4682.1562094810@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> writes:
> On Tue, Jul 2, 2019 at 9:19 PM Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru> wrote:
>> We could use commuted "const <-> var" operators for kNN searches, but the
>> current implementation requires the existence of "var <-> const" operators, and
>> order-by-op clauses are rebuilt using them (see match_clause_to_ordering_op()
>> at /src/backend/optimizer/path/indxpath.c).
> But probably it's still worth to just add commutator for every <->
> operator and close this question.
Yeah, I was just thinking that it was weird not to have the commutator
operators, independently of indexing considerations. Seems like a
usability thing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-07-02 19:56:18 | Re: [PATCH v5] Show detailed table persistence in \dt+ |
| Previous Message | Tom Lane | 2019-07-02 19:10:37 | Re: [PATCH v5] Show detailed table persistence in \dt+ |