- better to analyze large joins and sequential scan, and turn this parameter, e.g. reduce the size of effective_cache_size in postgresql.conf and change it for big queries.
This makes sense. We were setting it based on the tuning guideline from this page:
"Setting effective_cache_size to 1/2 of total memory would be a normal conservative setting, and 3/4 of memory is a more aggressive but still reasonable amount."