pg.ddx.io pgvector/pgvector GitHub issues and pull requests
help / color / mirror / Atom feed[pgvector/pgvector] PR #1067: [Arm CPU] Add SVE2 distance functions for halfvec on AArch64
2026-11-18 06:28 UTC "abhijain1204fujitsu (@abhijain1204fujitsu)" <noreply+abhijain1204fujitsu@github.com>
` Re: [pgvector/pgvector] PR #1067: [Arm CPU] Add SVE2 distance functions for halfvec on AArch64
2026-11-18 21:50 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #1067: [Arm CPU] Add SVE2 distance functions for halfvec on AArch64
2026-11-18 22:14 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #1067: [Arm CPU] Add SVE2 distance functions for halfvec on AArch64
2026-11-19 02:27 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #1067: [Arm CPU] Add SVE2 distance functions for halfvec on AArch64
2026-11-19 05:33 UTC "mohakgoel1 (@mohakgoel1)" <noreply+mohakgoel1@github.com>
` Re: [pgvector/pgvector] PR #1067: [Arm CPU] Add SVE2 distance functions for halfvec on AArch64
2026-11-19 05:45 UTC "mohakgoel1 (@mohakgoel1)" <noreply+mohakgoel1@github.com>
` Re: [pgvector/pgvector] PR #1067: [Arm CPU] Add SVE2 distance functions for halfvec on AArch64
2026-11-20 12:07 UTC "ankane (@ankane)" <noreply+ankane@github.com>
[7+ messages in thread]
[pgvector/pgvector] issue #1069: Autodelete vector database embedding after a fixed timestep (TTL) ?
2026-11-19 21:18 UTC "dsatyam09 (@dsatyam09)" <noreply+dsatyam09@github.com>
` Re: [pgvector/pgvector] issue #1069: Autodelete vector database embedding after a fixed timestep (TTL) ?
2026-11-19 21:30 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1069: Autodelete vector database embedding after a fixed timestep (TTL) ?
2026-11-19 21:30 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1069: Autodelete vector database embedding after a fixed timestep (TTL) ?
2026-11-20 00:21 UTC "dsatyam09 (@dsatyam09)" <noreply+dsatyam09@github.com>
` Re: [pgvector/pgvector] issue #1069: Autodelete vector database embedding after a fixed timestep (TTL) ?
2026-11-20 00:27 UTC "ankane (@ankane)" <noreply+ankane@github.com>
[5+ messages in thread]
[pgvector/pgvector] PR #1058: Improved performance of IVFFlat index scans
2026-11-05 22:40 UTC "Waterpine (@Waterpine)" <noreply+Waterpine@github.com>
` Re: [pgvector/pgvector] PR #1058: Improved performance of IVFFlat index scans
2026-11-11 07:11 UTC "Waterpine (@Waterpine)" <noreply+Waterpine@github.com>
` Re: [pgvector/pgvector] PR #1058: Improved performance of IVFFlat index scans
2026-11-17 10:51 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #1058: Improved performance of IVFFlat index scans
2026-11-17 23:23 UTC "Waterpine (@Waterpine)" <noreply+Waterpine@github.com>
` Re: [pgvector/pgvector] PR #1058: Improved performance of IVFFlat index scans
2026-11-18 00:06 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #1058: Improved performance of IVFFlat index scans
2026-11-18 05:45 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #1058: Improved performance of IVFFlat index scans
2026-11-18 05:47 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #1058: Improved performance of IVFFlat index scans
2026-11-18 10:34 UTC "ankane (@ankane)" <noreply+ankane@github.com>
[8+ messages in thread]
[pgvector/pgvector] issue #1068: [BUG] Iterative HNSW scan during vacuum fails with `ERROR: cannot load deleted element`
2026-11-18 06:40 UTC "Wwwing301 (@Wwwing301)" <noreply+Wwwing301@github.com>
` Re: [pgvector/pgvector] issue #1068: [BUG] Iterative HNSW scan during vacuum fails with `ERROR: cannot load deleted element`
2026-11-18 06:44 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1068: [BUG] Iterative HNSW scan during vacuum fails with `ERROR: cannot load deleted element`
2026-11-18 06:44 UTC "ankane (@ankane)" <noreply+ankane@github.com>
[3+ messages in thread]
[pgvector/pgvector] issue #1066: sum(halfvec) accumulates significant rounding errors and reverses exact L2 nearest-neighbor rankings
2026-11-18 00:45 UTC "leemeii (@leemeii)" <noreply+leemeii@github.com>
[pgvector/pgvector] issue #1065: Support for Advanced K-means Acceleration Techniques in IVFFlat Index Construction
2026-11-16 13:44 UTC "SunnyBo0302 (@SunnyBo0302)" <noreply+SunnyBo0302@github.com>
` Re: [pgvector/pgvector] issue #1065: Support for Advanced K-means Acceleration Techniques in IVFFlat Index Construction
2026-11-16 20:50 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1065: Support for Advanced K-means Acceleration Techniques in IVFFlat Index Construction
2026-11-17 04:21 UTC "SunnyBo0302 (@SunnyBo0302)" <noreply+SunnyBo0302@github.com>
` Re: [pgvector/pgvector] issue #1065: Support for Advanced K-means Acceleration Techniques in IVFFlat Index Construction
2026-11-17 19:12 UTC "saolof (@saolof)" <noreply+saolof@github.com>
[4+ messages in thread]
[pgvector/pgvector] issue #1043: bit Jaccard distance returns 1.0 for identical all-zero bit vectors
2026-10-20 03:24 UTC "JoeyLYZ666 (@JoeyLYZ666)" <noreply+JoeyLYZ666@github.com>
` Re: [pgvector/pgvector] issue #1043: bit Jaccard distance returns 1.0 for identical all-zero bit vectors
2026-10-20 04:04 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1043: bit Jaccard distance returns 1.0 for identical all-zero bit vectors
2026-10-20 04:04 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1043: bit Jaccard distance returns 1.0 for identical all-zero bit vectors
2026-10-20 09:00 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1043: bit Jaccard distance returns 1.0 for identical all-zero bit vectors
2026-10-20 09:00 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1043: bit Jaccard distance returns 1.0 for identical all-zero bit vectors
2026-10-30 18:23 UTC "duongynhi000005-oss (@duongynhi000005-oss)" <noreply+duongynhi000005-oss@github.com>
` Re: [pgvector/pgvector] issue #1043: bit Jaccard distance returns 1.0 for identical all-zero bit vectors
2026-11-16 11:05 UTC "catidegla (@catidegla)" <noreply+catidegla@github.com>
[7+ messages in thread]
[pgvector/pgvector] issue #1064: Corrupted index prevent table update
2026-11-14 01:06 UTC "juchiast (@juchiast)" <noreply+juchiast@github.com>
` Re: [pgvector/pgvector] issue #1064: Corrupted index prevent table update
2026-11-14 01:11 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1064: Corrupted index prevent table update
2026-11-14 01:41 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1064: Corrupted index prevent table update
2026-11-14 01:41 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1064: Corrupted index prevent table update
2026-11-14 02:37 UTC "juchiast (@juchiast)" <noreply+juchiast@github.com>
[5+ messages in thread]
[pgvector/pgvector] PR #1063: Switched to TidStore for HNSW vacuuming for Postgres 17+
2026-11-12 11:47 UTC "YidaWeng (@YidaWeng)" <noreply+YidaWeng@github.com>
` Re: [pgvector/pgvector] PR #1063: Switched to TidStore for HNSW vacuuming for Postgres 17+
2026-11-12 19:24 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #1063: Switched to TidStore for HNSW vacuuming for Postgres 17+
2026-11-12 19:24 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #1063: Switched to TidStore for HNSW vacuuming for Postgres 17+
2026-11-13 06:46 UTC "YidaWeng (@YidaWeng)" <noreply+YidaWeng@github.com>
[4+ messages in thread]
[pgvector/pgvector] PR #1061: Changed default for ivfflat.probes to sqrt(lists)
2026-11-11 15:57 UTC "YidaWeng (@YidaWeng)" <noreply+YidaWeng@github.com>
` Re: [pgvector/pgvector] PR #1061: Changed default for ivfflat.probes to sqrt(lists)
2026-11-11 19:00 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #1061: Changed default for ivfflat.probes to sqrt(lists)
2026-11-11 19:00 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #1061: Changed default for ivfflat.probes to sqrt(lists)
2026-11-13 06:46 UTC "YidaWeng (@YidaWeng)" <noreply+YidaWeng@github.com>
[4+ messages in thread]
[pgvector/pgvector] issue #1003: Support RabitQ in pgvector
2026-07-28 08:58 UTC "zthhhhh (@zthhhhh)" <noreply+zthhhhh@github.com>
` Re: [pgvector/pgvector] issue #1003: Support RabitQ in pgvector
2026-07-28 17:47 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1003: Support RabitQ in pgvector
2026-07-29 03:18 UTC "zthhhhh (@zthhhhh)" <noreply+zthhhhh@github.com>
` Re: [pgvector/pgvector] issue #1003: Support RabitQ in pgvector
2026-07-29 09:07 UTC "zthhhhh (@zthhhhh)" <noreply+zthhhhh@github.com>
` Re: [pgvector/pgvector] issue #1003: Support RabitQ in pgvector
2026-07-29 23:45 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1003: Support RabitQ in pgvector
2026-07-30 06:58 UTC "zthhhhh (@zthhhhh)" <noreply+zthhhhh@github.com>
` Re: [pgvector/pgvector] issue #1003: Support RabitQ in pgvector
2026-09-18 09:59 UTC "R3gardless (@R3gardless)" <noreply+R3gardless@github.com>
` Re: [pgvector/pgvector] issue #1003: Support RabitQ in pgvector
2026-10-23 17:01 UTC "gouyt13 (@gouyt13)" <noreply+gouyt13@github.com>
` Re: [pgvector/pgvector] issue #1003: Support RabitQ in pgvector
2026-10-26 08:28 UTC "zthhhhh (@zthhhhh)" <noreply+zthhhhh@github.com>
` Re: [pgvector/pgvector] issue #1003: Support RabitQ in pgvector
2026-11-03 06:23 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1003: Support RabitQ in pgvector
2026-11-09 20:12 UTC "txfs19260817 (@txfs19260817)" <noreply+txfs19260817@github.com>
` Re: [pgvector/pgvector] issue #1003: Support RabitQ in pgvector
2026-11-12 00:54 UTC "ankane (@ankane)" <noreply+ankane@github.com>
[12+ messages in thread]
[pgvector/pgvector] issue #1062: LNK1112: x64 object files conflict with x86 target when building pgvector on PostgreSQL 18.6 (Windows)
2026-11-11 20:33 UTC "jtb0964 (@jtb0964)" <noreply+jtb0964@github.com>
` Re: [pgvector/pgvector] issue #1062: LNK1112: x64 object files conflict with x86 target when building pgvector on PostgreSQL 18.6 (Windows)
2026-11-11 20:40 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1062: LNK1112: x64 object files conflict with x86 target when building pgvector on PostgreSQL 18.6 (Windows)
2026-11-11 20:40 UTC "ankane (@ankane)" <noreply+ankane@github.com>
[3+ messages in thread]
[pgvector/pgvector] PR #1060: Added search parameters to EXPLAIN settings
2026-11-11 07:47 UTC "karlmoriaty (@karlmoriaty)" <noreply+karlmoriaty@github.com>
` Re: [pgvector/pgvector] PR #1060: Added search parameters to EXPLAIN settings
2026-11-11 07:55 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #1060: Added search parameters to EXPLAIN settings
2026-11-11 07:55 UTC "ankane (@ankane)" <noreply+ankane@github.com>
[3+ messages in thread]
[pgvector/pgvector] PR #1059: Improved performance of inner product and cosine distance for sparsevec
2026-11-05 23:17 UTC "Waterpine (@Waterpine)" <noreply+Waterpine@github.com>
` Re: [pgvector/pgvector] PR #1059: Improved performance of inner product and cosine distance for sparsevec
2026-11-11 07:11 UTC "Waterpine (@Waterpine)" <noreply+Waterpine@github.com>
[2+ messages in thread]
[pgvector/pgvector] PR #86: Ivf index prefetch
2023-04-06 15:07 UTC "knizhnik (@knizhnik)" <noreply+knizhnik@github.com>
` Re: [pgvector/pgvector] PR #86: Ivf index prefetch
2023-04-11 05:13 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #86: Ivf index prefetch
2023-04-12 11:11 UTC "knizhnik (@knizhnik)" <noreply+knizhnik@github.com>
` Re: [pgvector/pgvector] PR #86: Ivf index prefetch
2023-05-21 00:19 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #86: Ivf index prefetch
2023-05-21 11:11 UTC "knizhnik (@knizhnik)" <noreply+knizhnik@github.com>
` Re: [pgvector/pgvector] PR #86: Ivf index prefetch
2023-05-24 01:07 UTC "jkatz (@jkatz)" <noreply+jkatz@github.com>
` Re: [pgvector/pgvector] PR #86: Ivf index prefetch
2023-05-24 06:05 UTC "knizhnik (@knizhnik)" <noreply+knizhnik@github.com>
` Re: [pgvector/pgvector] PR #86: Ivf index prefetch
2023-08-27 21:00 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #86: Ivf index prefetch
2023-08-27 21:00 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #86: Ivf index prefetch
2026-11-09 02:08 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #86: Ivf index prefetch
2026-11-09 06:34 UTC "ankane (@ankane)" <noreply+ankane@github.com>
[11+ messages in thread]
[pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2025-01-20 10:02 UTC "VladlenPopolitov (@VladlenPopolitov)" <noreply+VladlenPopolitov@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2025-01-20 19:52 UTC "jkatz (@jkatz)" <noreply+jkatz@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2025-01-21 03:42 UTC "VoVAllen (@VoVAllen)" <noreply+VoVAllen@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2025-01-29 07:04 UTC "VladlenPopolitov (@VladlenPopolitov)" <noreply+VladlenPopolitov@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2025-01-29 07:21 UTC "VladlenPopolitov (@VladlenPopolitov)" <noreply+VladlenPopolitov@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2025-02-09 00:00 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2025-02-21 00:31 UTC "michaelbautin (@michaelbautin)" <noreply+michaelbautin@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2025-03-11 06:18 UTC "VladlenPopolitov (@VladlenPopolitov)" <noreply+VladlenPopolitov@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2025-03-11 06:21 UTC "VladlenPopolitov (@VladlenPopolitov)" <noreply+VladlenPopolitov@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2025-07-25 19:02 UTC "DavidMelnychuk (@DavidMelnychuk)" <noreply+DavidMelnychuk@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2026-05-26 10:08 UTC "IgnazioDS (@IgnazioDS)" <noreply+IgnazioDS@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2026-05-26 14:05 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2026-06-18 19:14 UTC "cschanhniem (@cschanhniem)" <noreply+cschanhniem@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2026-08-03 09:37 UTC "anuj-kukunarapu (@anuj-kukunarapu)" <noreply+anuj-kukunarapu@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2026-08-04 05:51 UTC "zthhhhh (@zthhhhh)" <noreply+zthhhhh@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2026-08-14 00:37 UTC "jiahuijiang (@jiahuijiang)" <noreply+jiahuijiang@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2026-08-18 09:42 UTC "OmkarPalika (@OmkarPalika)" <noreply+OmkarPalika@github.com>
` Re: [pgvector/pgvector] issue #761: Enhancement: multicolumn vector index design
2026-11-06 10:10 UTC "klenioaraujo (@klenioaraujo)" <noreply+klenioaraujo@github.com>
[18+ messages in thread]
[pgvector/pgvector] issue #1057: Cosine distance returns NaN or incorrect finite values for finite nonzero vectors
2026-11-04 02:38 UTC "yzxxxx888 (@yzxxxx888)" <noreply+yzxxxx888@github.com>
` Re: [pgvector/pgvector] issue #1057: Cosine distance returns NaN or incorrect finite values for finite nonzero vectors
2026-11-04 02:54 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1057: Cosine distance returns NaN or incorrect finite values for finite nonzero vectors
2026-11-04 02:54 UTC "ankane (@ankane)" <noreply+ankane@github.com>
[3+ messages in thread]
[pgvector/pgvector] PR #1056: Fixed Jaccard distance for two empty bit vectors
2026-11-03 13:44 UTC "Ksschkw (@Ksschkw)" <noreply+Ksschkw@github.com>
` Re: [pgvector/pgvector] PR #1056: Fixed Jaccard distance for two empty bit vectors
2026-11-03 17:34 UTC "Ksschkw (@Ksschkw)" <noreply+Ksschkw@github.com>
` Re: [pgvector/pgvector] PR #1056: Fixed Jaccard distance for two empty bit vectors
2026-11-03 18:39 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] PR #1056: Fixed Jaccard distance for two empty bit vectors
2026-11-03 18:39 UTC "ankane (@ankane)" <noreply+ankane@github.com>
[4+ messages in thread]
[pgvector/pgvector] issue #1055: HNSW under SERIALIZABLE: two concurrent check-then-insert transactions can both commit
2026-11-02 01:49 UTC "anonymous-ai-researcher (@anonymous-ai-researcher)" <noreply+anonymous-ai-researcher@github.com>
` Re: [pgvector/pgvector] issue #1055: HNSW under SERIALIZABLE: two concurrent check-then-insert transactions can both commit
2026-11-02 03:19 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1055: HNSW under SERIALIZABLE: two concurrent check-then-insert transactions can both commit
2026-11-02 21:46 UTC "ankane (@ankane)" <noreply+ankane@github.com>
[3+ messages in thread]
[pgvector/pgvector] PR #1054: Plan: immutable forward and inverted indexes sharing the GPU worker's ordinals
2026-11-01 14:52 UTC "chenqin (@chenqin)" <noreply+chenqin@github.com>
` Re: [pgvector/pgvector] PR #1054: Plan: immutable forward and inverted indexes sharing the GPU worker's ordinals
2026-11-01 14:52 UTC "chenqin (@chenqin)" <noreply+chenqin@github.com>
[2+ messages in thread]
[pgvector/pgvector] PR #1053: Serve loaded indexes to many PostgreSQL hosts over the network
2026-10-31 14:05 UTC "chenqin (@chenqin)" <noreply+chenqin@github.com>
` Re: [pgvector/pgvector] PR #1053: Serve loaded indexes to many PostgreSQL hosts over the network
2026-10-31 14:05 UTC "chenqin (@chenqin)" <noreply+chenqin@github.com>
[2+ messages in thread]
[pgvector/pgvector] issue #1050: Rebuild pg16 image for Debian Perl and Go stdlib security fixes
2026-10-31 08:36 UTC "iniTwakkie (@iniTwakkie)" <noreply+iniTwakkie@github.com>
` Re: [pgvector/pgvector] issue #1050: Rebuild pg16 image for Debian Perl and Go stdlib security fixes
2026-10-31 10:19 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1050: Rebuild pg16 image for Debian Perl and Go stdlib security fixes
2026-10-31 10:19 UTC "ankane (@ankane)" <noreply+ankane@github.com>
[3+ messages in thread]
[pgvector/pgvector] issue #1052: [Bug] Sparse scalar distances overflow on finite `sparse
2026-10-31 08:56 UTC "JoeyLYZ666 (@JoeyLYZ666)" <noreply+JoeyLYZ666@github.com>
` Re: [pgvector/pgvector] issue #1052: [Bug] Sparse scalar distances overflow on finite `sparse
2026-10-31 09:45 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1052: [Bug] Sparse scalar distances overflow on finite `sparse
2026-10-31 09:45 UTC "ankane (@ankane)" <noreply+ankane@github.com>
[3+ messages in thread]
[pgvector/pgvector] issue #1051: [Bug] Dense scalar distances overflow on finite `vector` inputs
2026-10-31 08:55 UTC "JoeyLYZ666 (@JoeyLYZ666)" <noreply+JoeyLYZ666@github.com>
` Re: [pgvector/pgvector] issue #1051: [Bug] Dense scalar distances overflow on finite `vector` inputs
2026-10-31 09:45 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1051: [Bug] Dense scalar distances overflow on finite `vector` inputs
2026-10-31 09:45 UTC "ankane (@ankane)" <noreply+ankane@github.com>
[3+ messages in thread]
[pgvector/pgvector] issue #1049: sparsevec rejects semantically empty input with more than 16,000 explicit zero fields
2026-10-26 13:19 UTC "leemeii (@leemeii)" <noreply+leemeii@github.com>
` Re: [pgvector/pgvector] issue #1049: sparsevec rejects semantically empty input with more than 16,000 explicit zero fields
2026-10-26 21:10 UTC "ankane (@ankane)" <noreply+ankane@github.com>
` Re: [pgvector/pgvector] issue #1049: sparsevec rejects semantically empty input with more than 16,000 explicit zero fields
2026-10-26 21:12 UTC "ankane (@ankane)" <noreply+ankane@github.com>
[3+ messages in thread]
[next (older)]
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