This content is originally from my own blog. Check it out here!
hi :3
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
asfdada
asdasfa
**asfdasfa
**
a
b
c
a1
b2
c3
`aaa`
```js
const a = 12;
```
test
huh guh
There are two relevant indexes in that table: one on (repo, time) (repo = user's DID), and one on just (time). Roughly speaking, for those users who follow e.g. 80 or 200 people, it makes more sense to scan the (repo, time) index those 80-200 times and collect the 100 most recent posts from all of those found, and for those who follow e.g. 9000 (yes, that happens 😛), it's faster to scan the single (time) index until you find 100 relevant posts. But I've been struggling to make Postgres always use the right index.