pg.ddx.io  pgvector/pgvector GitHub issues and pull requests  
help / color / mirror / Atom feed
[pgvector/pgvector] issue #1052: [Bug] Sparse scalar distances overflow on finite `sparse
3+ messages / 2 participants
[nested] [flat]

* [pgvector/pgvector] issue #1052: [Bug] Sparse scalar distances overflow on finite `sparse
@ 2026-10-31 08:56  "JoeyLYZ666 (@JoeyLYZ666)" <noreply+JoeyLYZ666@github.com>
  0 siblings, 0 replies; 3+ messages in thread

From: JoeyLYZ666 (@JoeyLYZ666) @ 2026-10-31 08:56 UTC (permalink / raw)
  To: pgvector/pgvector <noreply+pgvector-pgvector@github.com>

## Describe the bug

pgvector 0.8.7 returns `Infinity` or `NaN` from sparsevec scalar distance
functions for finite nonzero elements whose exact result is representable by
`double precision`.

## Reproduce

Run `testcase.py` against PostgreSQL with pgvector 0.8.7:

```powershell
python testcase.py
```

The testcase compares two finite `sparsevec(2)` values with opposite `1e38`
components and computes L1, L2, and self cosine distance.

[testcase.py](https://github.com/user-attachments/files/34213348/testcase.py)

## Expected behavior

The expected results are finite: approximately `4e38`, `2.828427e38`, and `0`
for self cosine distance.

## Actual behavior

The affected release returns:

```text
Infinity, Infinity, NaN
```

The sparsevec implementation accumulates intermediate values in `float` before
returning `double precision`.

## Impact

Finite sparse vectors can produce non-finite or invalid distances, breaking
ordering, thresholds, and scalar correctness checks.

## Environment

- pgvector 0.8.7
- PostgreSQL 18
- `sparsevec(2)` values

`vector.c` report because the SQL type and implementation path differ.


^ permalink  raw  [nested|flat] 3+ messages in thread

* Re: [pgvector/pgvector] issue #1052: [Bug] Sparse scalar distances overflow on finite `sparse
@ 2026-10-31 09:45  "ankane (@ankane)" <noreply+ankane@github.com>
  1 sibling, 0 replies; 3+ messages in thread

From: ankane (@ankane) @ 2026-10-31 09:45 UTC (permalink / raw)
  To: pgvector/pgvector <noreply+pgvector-pgvector@github.com>

Hi @JoeyLYZ666, see https://github.com/pgvector/pgvector/issues/1033#issuecomment-5884285142.

^ permalink  raw  [nested|flat] 3+ messages in thread

* Re: [pgvector/pgvector] issue #1052: [Bug] Sparse scalar distances overflow on finite `sparse
@ 2026-10-31 09:45  "ankane (@ankane)" <noreply+ankane@github.com>
  1 sibling, 0 replies; 3+ messages in thread

From: ankane (@ankane) @ 2026-10-31 09:45 UTC (permalink / raw)
  To: pgvector/pgvector <noreply+pgvector-pgvector@github.com>

@ankane closed this.

^ permalink  raw  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2026-10-31 09:45 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-10-31 08:56 [pgvector/pgvector] issue #1052: [Bug] Sparse scalar distances overflow on finite `sparse "JoeyLYZ666 (@JoeyLYZ666)" <noreply+JoeyLYZ666@github.com>
2026-10-31 09:45 ` "ankane (@ankane)" <noreply+ankane@github.com>
2026-10-31 09:45 ` "ankane (@ankane)" <noreply+ankane@github.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox