Andrew Kane
Andrew Kane
Thanks @tureba, the additional context I added was probably more confusing than helpful. Your PR should both fix the flags and set the SDK/sysroot to a major version.
Hi @bantmen, if you're testing performance on a snapshot, [lazy loading](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_RestoreFromSnapshot.html) could be the issue. > If you access data that hasn't been loaded yet, the DB instance immediately downloads...
If lazy loading isn't the issue, just prewarming the index should be fine. I agree figuring out what's going on with I/O is a good first step.
Cleaning up issues (don't think there's anything for pgvector to do here).
Thanks @hlinnaka, makes sense to me. Going to wait until 0.8.0 to merge since it's a slightly breaking change.
Starting to merge 0.8.0 work. Thanks again @hlinnaka!
Tried disabling JIT and the error goes away, fwiw.
Awesome, thanks @headius!
Makes sense. I think it should probably always include the precision in that case.
The test failure seems to be from a flaky test (also in [this CI run](https://github.com/rails/solid_queue/actions/runs/13512426459/job/37755039880) from February).