| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | "S, Naveen Krishna (Development Engineer 3)" <naveenkrishna(dot)s(at)sky(dot)uk> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [EXTERNAL] Re: BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors |
| Date: | 2025-11-19 20:22:12 |
| Message-ID: | CA+hUKGK9NOiaORdsSFLK6sJCsrAmtkU3m4+KX9PM5nPwTtJMPQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Nov 19, 2025 at 10:55 PM S, Naveen Krishna (Development
Engineer 3) <naveenkrishna(dot)s(at)sky(dot)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):
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ocean_li_996 | 2025-11-20 18:16:17 | Re: BUG #19109: catalog lookup with the wrong snapshot duringlogical decoding causes coredump |
| Previous Message | Heikki Linnakangas | 2025-11-19 16:08:22 | Re: pg_resetwal prints new OldestXID in wrong circumstances |