rw-access

4 ms·

1. 1.▲
   by rw-access 2y ago

   I have hundreds of queries like this in production (Go + Postgres + pgx), and don't have issues leveraging the right indexes. Make sure when using prepared statements, you have custom query plans per query for this via `SET plan_cache_
2. 2.▲
   by rw-access 2y ago

   The CLA best answers the questions in your first paragraph. https://www.elastic.co/contributor-agreement
3. 3.▲
   by rw-access 3y ago

   Assuming the MxN claim was accurate, yeah. The author of this post wrote a prior one [1], challenging whether MxN was truly the problem LSP was solving. It's also a good read! https://matklad.github.io/2022/04&#x2
4. 4.▲
   by rw-access 3y ago

   That's part of the protocol with a Document highlight request. Basically if you click on a symbol in the client, it'll send the server side request where it can find all references and mark which ones are read and which are write.
5. 5.▲
   Full-text search engine with PostgreSQL (part 2): Postgres vs. Elasticsearch(xata.io)

   110 points by rw-access 3y ago|16 comments