alt Hacker News> Which postgres specific schema/query features do you use to significantly improve performance?
Erm. Isn't this kind of a schema specific question ?
I mean, sometimes I see schemas that are so goddam awful that the answer to your question would be "anything, literally anything".
Other times its the old story of failing to use or misconfiguring indexes.
And then, yes you end up in the realms of Postgres specific stuff. What you do there clearly depends on what you're looking at.
But the point is, I could probably count on one hand the number of times the problem has been "the storage" or "the database". Most of the time its "the developer". :D
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.