PGVectorHelper instances have a connection, which renders their methods non-reentrant. I ran into this last night in the form of
asyncpg.exceptions._base.InterfaceError: cannot perform operation: another operation is in progress
Since DB connections are stateful, this is a classic use-case for a connection pool. Furthermore, it's bad that PGVectorHelper instances hold upon a connection for an indefinite, and possibly long time.
PGVectorHelper instances have a connection, which renders their methods non-reentrant. I ran into this last night in the form of
Since DB connections are stateful, this is a classic use-case for a connection pool. Furthermore, it's bad that PGVectorHelper instances hold upon a connection for an indefinite, and possibly long time.