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
{{ message }}
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
Currently, the codebase uses Binary Trees for indices. This can be optimized by implementing Generalized Search Trees instead. This will help scale tag searches and reduce bloat in the indices as well too.
Solution
There are a couple moving components to the project. We would need to enable GIST by running the SQL command.
CREATE EXTENSION btree_gist;
In development, this is fairly trivial as you can just ssh into Postgres and run the command. However, with docker-compose we would need to have a bootsql script to run this command as an adminstrator.
After, all indices that are VARCHAR should be upgraded to GIST as opposed to HASH or BTREE.
Description
Currently, the codebase uses Binary Trees for indices. This can be optimized by implementing Generalized Search Trees instead. This will help scale tag searches and reduce bloat in the indices as well too.
Solution
There are a couple moving components to the project. We would need to enable
GIST
by running the SQL command.In development, this is fairly trivial as you can just ssh into Postgres and run the command. However, with
docker-compose
we would need to have aboot
sql
script to run this command as an adminstrator.After, all indices that are
VARCHAR
should be upgraded toGIST
as opposed toHASH
orBTREE
.Reference
The text was updated successfully, but these errors were encountered: