From: | Edson Richter <edsonrichter(at)hotmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgres as In-Memory Database? |
Date: | 2013-11-17 13:42:09 |
Message-ID: | BLU0-SMTP64973D75A470AD792CA15ECFE50@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Em 17/11/2013 10:00, Michael Paquier escreveu:
> On Sun, Nov 17, 2013 at 8:25 PM, Stefan Keller <sfkeller(at)gmail(dot)com> 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,
One question: would you please expand your answer and explain how would
this adversely affect async replication?
Edson
From | Date | Subject | |
---|---|---|---|
Next Message | rob stone | 2013-11-17 14:15:11 | Re: Postgres as In-Memory Database? |
Previous Message | Michael Paquier | 2013-11-17 12:00:05 | Re: Postgres as In-Memory Database? |