Re: BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors - Mailing list pgsql-bugs

From Thomas Munro
Subject Re: BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors
Date
Msg-id CA+hUKGJVFZW2A4jWZTxdsG=8Rm8O+YUn2UHTUZVKtR+ukjgPhQ@mail.gmail.com
Whole thread Raw
In response to BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: [EXTERNAL] Re: BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors
List pgsql-bugs
On Mon, Nov 17, 2025 at 7:14 PM PG Bug reporting form
<noreply@postgresql.org> wrote:
> 40 records

Sounds like pgvector[1]?

"Why are there less results for a query after adding an HNSW index?
Results are limited by the size of the dynamic candidate list
(hnsw.ef_search), which is 40 by default. ...."

[1] https://github.com/pgvector/pgvector



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors
Next
From: "Haowu Ge"
Date:
Subject: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)