TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Reading Large Postgres Tables – Top Lessons We Learned

1 pointsby makaimcalmost 2 years ago

1 comment

franckpachotalmost 2 years ago
I&#x27;m not sure those are great recommendations. First, the range scan on Tid is there only since PostgreSQL 14: <a href="https:&#x2F;&#x2F;commitfest.postgresql.org&#x2F;32&#x2F;2924&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;commitfest.postgresql.org&#x2F;32&#x2F;2924&#x2F;</a> And the CTID changes on an active database: <a href="https:&#x2F;&#x2F;twitter.com&#x2F;FranckPachot&#x2F;status&#x2F;1691021274829426688?s=20" rel="nofollow noreferrer">https:&#x2F;&#x2F;twitter.com&#x2F;FranckPachot&#x2F;status&#x2F;1691021274829426688?...</a>