/explore
|
You are here 
|
blog.soykaf.com | ||
| | | | |
www.rorvswild.com
|
|
| | | | | Querying your database across associations can become a bottleneck in your Rails application. Julian Rubisch, our first guest author, explains why and suggests an efficient solution. | |
| | | | |
jkatz.github.io
|
|
| | | | | An example of how to perform hybrid search with PostgreSQL and pgvector over vector data. | |
| | | | |
abuisman.com
|
|
| | | | | Blog about solving problems with code, mostly Ruby, and other things I have learned working as an engineer and a technical leader | |
| | | | |
jazco.dev
|
|
| | | Postgres uses an internal table called 'pg_statistic' to keep track of some metadata on all tables in the DB. Postgres's Planner uses these statistics when estimating the cost of operations, which, if out of date, can cause the Planner to pick a suboptimal plan for our query. To trigger an update of 'pg_statistic' manually for a table, we can run 'ANALYZE' on it, helping the Planner estimate costs better and speeding up queries dramatically (in some cases). | ||
