Re: BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: naveenkrishna(dot)s(at)sky(dot)uk, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors
Date: 2025-11-17 07:50:45
Message-ID: CA+hUKGJVFZW2A4jWZTxdsG=8Rm8O+YUn2UHTUZVKtR+ukjgPhQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Nov 17, 2025 at 7:14 PM PG Bug reporting form
<noreply(at)postgresql(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Haowu Ge 2025-11-17 08:02:21 GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
Previous Message PG Bug reporting form 2025-11-17 06:08:30 BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors