Re: Running PostgreSQL as fast as possible no matter the consequences - Mailing list pgsql-performance

From A B
Subject Re: Running PostgreSQL as fast as possible no matter the consequences
Date
Msg-id AANLkTim6fh-DJHsBucmMPUX9Luwd20sRHJ7SP4nabL7Z@mail.gmail.com
Whole thread Raw
In response to Re: Running PostgreSQL as fast as possible no matter the consequences  (Craig Ringer <craig@postnewspapers.com.au>)
List 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.

pgsql-performance by date:

Previous
From: A B
Date:
Subject: Re: Running PostgreSQL as fast as possible no matter the consequences
Next
From: Marti Raudsepp
Date:
Subject: Re: Running PostgreSQL as fast as possible no matter the consequences