On 10/28/16 2:33 PM, Joshua D. Drake wrote:
* A very high shared_buffers (in newer releases, it is not uncommon to have many, many GB of)
Keep in mind that you might get very poor results if shared_buffers is large, but not large enough to fit the entire database. In that case buffer replacement will be *extremely* expensive. Some operations will use a different buffer replacement strategy, so you might be OK if some of the database doesn't fit in shared buffers; that will depend a lot on your access patterns.
-- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com 855-TREBLE2 (855-873-2532) mobile: 512-569-9461 -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
