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

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: A B <gentosaker(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Running PostgreSQL as fast as possible no matter the consequences
Date: 2010-11-05 11:27:41
Message-ID: 4CD3EA2D.3050403@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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/

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Marti Raudsepp 2010-11-05 11:30:41 Re: Running PostgreSQL as fast as possible no matter the consequences
Previous Message A B 2010-11-05 11:24:13 Re: Running PostgreSQL as fast as possible no matter the consequences