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

From Thom Brown
Subject Re: Running PostgreSQL as fast as possible no matter the consequences
Date
Msg-id AANLkTik0FBaJuG0yOO6MqCsYNYrW3rz1K5Uv0R71GBf8@mail.gmail.com
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
Re: Running PostgreSQL as fast as possible no matter the consequences
List pgsql-performance
On 5 November 2010 10:59, A B <gentosaker@gmail.com> 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?


Turn off fsync and full_page_writes (i.e. running with scissors).

Also depends on what you mean by "as fast as possible".  Fast at doing what?  Bulk inserts, selecting from massive tables?

--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935

pgsql-performance by date:

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