logoalt Hacker News

CodesInChaos • today at 11:45 AM • 0 replies • view on HN

The parent post emphasizes how portable schemas or queries cost performance. Now I understand important parts of the schema are postgres specific (e.g. the configuration of non-trivial indexes), but I think most of my queries happen to be portable. So I wondered where people sacrifice performance in the name of portability, and why that's so common that it's worth calling out.