this post was submitted on 19 Aug 2024
74 points (96.2% liked)
Programming
17423 readers
41 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Ah, thanks for linking that PR. The point made in the article is a good and helpful one, as can be seen by the way so many sites get it wrong, including Lemmy in the past. It's just that it is pretty thin to make a whole article around. It would be a good thing to bring up in an optimization guide that covers more topics.
I would be interested to know if there is substantial cost to keeping cursors open for long periods, while the db is being updated. I think given those labels, it may be preferable to do a new select each time the user requests the next page. But I haven't benchmarked that.
If you look at how Wikipedia pages through article histories, the labels are timestamps with 1 second resolution.
Here is another article about the same topic, part of the author's book on SQL performance:
https://use-the-index-luke.com/sql/partial-results/fetch-next-page