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

From Craig Ringer
Subject Re: Running PostgreSQL as fast as possible no matter the consequences
Date
Msg-id 4CD3EA2D.3050403@postnewspapers.com.au
Whole thread Raw
In response to Running PostgreSQL as fast as possible no matter the consequences  (A B <gentosaker@gmail.com>)
Responses Re: Running PostgreSQL as fast as possible no matter the consequences
List pgsql-performance
On 05/11/10 18:59, A B wrote:
> Hi there.
>
> 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.

--
Craig Ringer

Tech-related writing: http://soapyfrogs.blogspot.com/

pgsql-performance by date:

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