@tadano>Didn't find too much so far save for a ton of duplicate key value violates unique constraint errors.Unique constraint violations are normal, the are handled at the application level.>I don't know if that's specifically related to it, anything off the top of your head I should be looking for in regards to postgres aggresively caching?Even at 1G it is still < 10% of what you have, and so far there is no sign of any problem. I'd leave it as is.I can't tell you much about pg fine tuning, for that it would be better to consult with documentation https://www.postgresql.org/docs/current/runtime-config-resource.html