On Sun, Nov 17, 2013 at 09:00:05PM +0900, Michael Paquier wrote: > On Sun, Nov 17, 2013 at 8:25 PM, Stefan Keller <sfkeller@xxxxxxxxx> wrote: > > How can Postgres be used and configured as an In-Memory Database? > > > > Does anybody know of thoughts or presentations about this "NoSQL feature" - > > beyond e.g. "Perspectives on NoSQL" from Gavin Roy at PGCon 2010)? > > > > Given, say 128 GB memory or more, and (read-mostly) data that fit's into > > this, what are the hints to optimize Postgres (postgresql.conf etc.)? > In this case as you are trading system safety (system will not be > crash-safe) for performance... The following parameters would be > suited: > - Improve performance by reducing the amount of data flushed: > fsync = off > synchronous_commit=off > - Reduce the size of WALs: > full_page_writes = off > - Disable the background writer: > bgwriter_lru_maxpages = 0 > Regards, FYI, the Postgres manual covers non-durability settings: http://www.postgresql.org/docs/9.3/static/non-durability.html -- Bruce Momjian <bruce@xxxxxxxxxx> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
