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

From: Thom Brown <thom(at)linux(dot)com>
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:14:43
Message-ID: AANLkTik0FBaJuG0yOO6MqCsYNYrW3rz1K5Uv0R71GBf8@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 5 November 2010 10:59, A B <gentosaker(at)gmail(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Thom Brown 2010-11-05 11:15:51 Re: Running PostgreSQL as fast as possible no matter the consequences
Previous Message Guillaume Cottenceau 2010-11-05 11:11:25 Re: Running PostgreSQL as fast as possible no matter the consequences