Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH] kNN for btree - Mailing list pgsql-hackers

From Nikita Glukhov
Subject Re: [PATCH] kNN for btree
Date
Msg-id b8f5294c-b99a-9bb2-eeca-0a04d8b0a3a3@postgrespro.ru
Whole thread Raw
In response to Re: [PATCH] kNN for btree  (Michael Paquier <michael@paquier.xyz>)
Responses Re: [PATCH] kNN for btree  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
Tree view
On 04.02.2019 8:35, Michael Paquier wrote:
This patch set needs a rebase because of conflicts caused by the
recent patches for pluggable storage.

Attached 6th version of the patches rebased onto current master:
* index_clauses now also passed into ammatchorderby()
* added support for queries like  SELECT * FROM tab WHERE col1 = val1 AND col2 = val2 ORDER BY col3 <-> val3
* (experimental patch #9)  added support for queries like  SELECT * FROM tab WHERE col1 IN (v1, v2, v3) ORDER BY col1, col2 <-> val


Patch #9 is experimental.  In order to distinguish order-by-operator and 
simple order-by-column clauses (index column can be operator expression)
in orderbyclauses lists I am trying to pass negative column numbers in 
orderbyclausecols, but it looks ugly, so I think orderbyclauses passing needs
some refactoring like recent IndexClause refactoring.  Also I doubt that I 
correctly implemented match_pathkey_to_indexcol().

--
Nikita Glukhov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Attachment

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: CPU costs of random_zipfian in pgbench
Next
From: "Takahashi, Ryohei"
Date:
Subject: RE: SQL statement PREPARE does not work in ECPG