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

From Thomas Munro
Subject Re: [EXTERNAL] Re: BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors
Date
Msg-id CA+hUKGK9NOiaORdsSFLK6sJCsrAmtkU3m4+KX9PM5nPwTtJMPQ@mail.gmail.com
Whole thread Raw
In response to Re: [EXTERNAL] Re: BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors  ("S, Naveen Krishna (Development Engineer 3)" <naveenkrishna.s@sky.uk>)
List pgsql-bugs
On Wed, Nov 19, 2025 at 10:55 PM S, Naveen Krishna (Development
Engineer 3) <naveenkrishna.s@sky.uk> wrote:
> The issue is occurring when HNSW indexing is done.
> The issue is not replicable with vector extension 0.8.0
> I have tried with multiple m and ef_construction pairs ranging from (16,200) to (64,512) and nothing is working.
>
> May I know where could I see the release updates on 0.8.1 of the vector extension?
> Also please feel free to share your thoughts for me to test more on the same.

Hi Naveen,

pgvector is an independent project.  If you think it's misbehaving you
should probably raise an issue here (after reading all the
documentation):

https://github.com/pgvector/pgvector/issues



pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: pg_resetwal prints new OldestXID in wrong circumstances
Next
From: ocean_li_996
Date:
Subject: Re: BUG #19109: catalog lookup with the wrong snapshot duringlogical decoding causes coredump