Re: Running PostgreSQL as fast as possible no matter the consequences

From: A B <gentosaker(at)gmail(dot)com>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Running PostgreSQL as fast as possible no matter the consequences
Date: 2010-11-05 11:36:08
Message-ID: AANLkTim6fh-DJHsBucmMPUX9Luwd20sRHJ7SP4nabL7Z@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

>> If you just wanted PostgreSQL to go as fast as possible WITHOUT any
>> care for your data (you accept 100% dataloss and datacorruption if any
>> error should occur), what settings should you use then?
>
> Others have suggested appropriate parameters ("running with scissors").
>
> I'd like to add something else to the discussion: have you looked at
> memcached yet? Or pgpool? If you haven't, start there.
>

memcahced has been mentioned in some discussions, but I have not studied it yet.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Marti Raudsepp 2010-11-05 11:36:34 Re: Running PostgreSQL as fast as possible no matter the consequences
Previous Message A B 2010-11-05 11:32:39 Re: Running PostgreSQL as fast as possible no matter the consequences