Hello,
Thanks again for this wonderful product and the hard work you've put into it.
Do similarity filters restrict the range of records for SIREAD locks? i.e. when in a SERIALIZABLE transaction and issuing a query with a similarity filter condition (e.g. SELECT FROM vectors WHERE centroid <<#>> sphere($1::halfvec, $2)), can pgsql restrict the concurrency checks to the range of rows that fell within the $2 search radius for fine-grained locking or is the entire table marked for SIREAD locks? Do any inserts into vectors during this transaction cause the serializable query to fail or only those that fell into the search radius?
I'm guessing fine-grained locking isn't implemented, but it would be amazing if it were! Is this on the roadmap?
Hello,
Thanks again for this wonderful product and the hard work you've put into it.
Do similarity filters restrict the range of records for SIREAD locks? i.e. when in a SERIALIZABLE transaction and issuing a query with a similarity filter condition (e.g.
SELECT FROM vectors WHERE centroid <<#>> sphere($1::halfvec, $2)), can pgsql restrict the concurrency checks to the range of rows that fell within the$2search radius for fine-grained locking or is the entire table marked for SIREAD locks? Do any inserts intovectorsduring this transaction cause the serializable query to fail or only those that fell into the search radius?I'm guessing fine-grained locking isn't implemented, but it would be amazing if it were! Is this on the roadmap?