You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently usearch code uses the default allocator (malloc-based)
We should use palloc to make sure all memory is manged through postgres
We can do that by adding a field to usearch_init that will take a custom allocation function and will build a custom default allocator on it in usearch code
The text was updated successfully, but these errors were encountered:
Ngalstyan4
changed the title
Write a custom palloc-based memory allocator and pass it to usearch
Use proper palloc-based memory allocator in usearch
Sep 16, 2023
Currently usearch code uses the default allocator (malloc-based)
We should use palloc to make sure all memory is manged through postgres
We can do that by adding a field to
usearch_init
that will take a custom allocation function and will build a custom default allocator on it in usearch codeThe text was updated successfully, but these errors were encountered: