From: Craig Ringer <craig@postnewspapers.com.au>
To: A B <gentosaker@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Running PostgreSQL as fast as possible no matter the consequences
Date: Fri, 05 Nov 2010 19:27:41 +0800
Message-ID: <4CD3EA2D.3050403@postnewspapers.com.au> (raw)
In-Reply-To: <AANLkTimcUYuutQeThCaP-077reGYWwdq-ssKwbPne8TO@mail.gmail.com>
References: <AANLkTimcUYuutQeThCaP-077reGYWwdq-ssKwbPne8TO@mail.gmail.com>
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/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: craig@postnewspapers.com.au, gentosaker@gmail.com
Subject: Re: Running PostgreSQL as fast as possible no matter the consequences
In-Reply-To: <4CD3EA2D.3050403@postnewspapers.com.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox