[mhatipog]

Problem

SparseVector preserves JavaScript Map insertion order, but PostgreSQL sparsevec requires ascending coordinate indices. For an unordered Map, the generated literal is rejected with sparsevec indices must be in ascending order.

Fix

Sort numeric coordinate/value pairs together before populating indices and values. Do not mutate the input Map. This matches Python and Go pgvector clients.

Tests

• Update Map unit assertions for ordering, SQL output and dense values
• Add unordered Map regression with negative/zero values and input immutability
• Add PostgreSQL INSERT/RETURNING integration regression

Targeted Node tests passed on Repo Guardian runner; the PostgreSQL integration test is included for upstream CI.

[ankane]

Hi @mhatipog, the text format doesn't require this.