or are there any caveats or "gotchas" to be aware of?
# DB Type: mixed
But they are probably better than the generic defaults at least. The more pertinent question is whether you are getting good enough performance for the amount of effort spent or whether more effort, and customization to your exact situation, is needed to get even better performance. Because the standard caveat is that if you are not experimenting on production-like workloads the suggestions and/or data you are seeing will not be tailored to your production environment. It's nearly impossible to reduce the gap to zero, but pgTune still leaves a pretty sizable gap (though whether that matters depends, again, on the characteristics of the production environment).
