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

From Kirill Reshke
Subject Re: [PATCH] kNN for btree
Date
Msg-id CALdSSPiQhrtXaN-Doa0KypL2WKjQkByJPB9VBAK69CqW95kVeA@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] kNN for btree  ("Anton A. Melnikov" <a.melnikov@postgrespro.ru>)
List pgsql-hackers
On Wed, 31 Jul 2024 at 09:46, Anton A. Melnikov
<a.melnikov@postgrespro.ru> wrote:
>
> Hi!
>
> Rebased existing patch on current master to have an actual working version.
> There is an inconsistency with commit 5bf748b86.
>
> Reproduction:
> CREATE TABLE test (a int4);
> INSERT INTO test VALUES (2), (3);
> CREATE INDEX test_idx ON test USING btree(a);
> SET enable_seqscan = OFF;
> SELECT * FROM test WHERE a IN (2, 3) ORDER BY a <-> 5;
>
> Actual result:
> postgres=# SELECT * FROM test WHERE a IN (2, 3) ORDER BY a <-> 5;
>   a
> ---
>   3
> (1 row)
>
> Correct expected result:
> postgres=# SELECT * FROM test WHERE a IN (2, 3) ORDER BY a <-> 5;
>   a
> ---
>   3
>   2
> (2 rows)
>
> Reported an issue in the thread corresponding to commit 5bf748b86.
>
> With the best regards,
>
>
> --
> Anton A. Melnikov
> Postgres Professional: http://www.postgrespro.com
> The Russian Postgres Company
Hi!
Given little activity here, there is a little chance of being
committed in the current commitfest, so I moved to the next.

I will try to take a look at v19 soon.


-- 
Best regards,
Kirill Reshke



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Difference in dump from original and restored database due to NOT NULL constraints on children
Next
From: Dean Rasheed
Date:
Subject: Re: Adding OLD/NEW support to RETURNING