Andrew Kane

From my understanding, there will likely be a Postgres release this month that includes @VladlenPopolitov's fix. > The target date for these releases are, unless otherwise stated, the second Thursday...

Postgres 17.3 [has been released](https://www.postgresql.org/about/news/postgresql-173-167-1511-1416-and-1319-released-3015/) with the patch. Thanks again @VladlenPopolitov!

Hi @Issung, this looks like the same error as #31 and #41 (likely missing a call to `useVector` somewhere).

Looks like others have run into this as well: https://github.com/hangfire-postgres/Hangfire.PostgreSql/issues/316 It sounds like `Hangfire.PostgreSql` has the same issue with NodaTime and there's a workaround: https://github.com/hangfire-postgres/Hangfire.PostgreSql/issues/322#issuecomment-1710694316

We may be able to remove the `NpgsqlConnection.GlobalTypeMapper` call like other extensions did in https://github.com/npgsql/efcore.pg/pull/3167, which may fix it.

Switched to the new plugin approach in [this branch](https://github.com/pgvector/pgvector-dotnet/compare/config-plugin), but it requires EF Core 9.

@roji Thanks for taking a look. @Issung I probably won't merge / drop support for EF Core 8 until EF Core 10 is released, so I'd recommend using the workaround...

Merged the new plugin approach in the commit above.

Hi @SunnyBo0302, there's [a branch](https://github.com/pgvector/pgvector/compare/hnsw-read-stream) for this for HNSW. However, I saw a significant regression in performance with `io_method = worker` (the default for Postgres 18) on Linux when the...

Hi @zthhhhh, thanks for the PR. It'd be good to see how performance compares to the existing quantization options (half-precision indexing and binary quantization with re-ranking), as well as int8...