| 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:15:51 |
| Message-ID: | AANLkTikzrFyQMtEMAu0ok1mrvy5D_LTSTDs7gmB0nMmD@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 5 November 2010 11:14, Thom Brown <thom(at)linux(dot)com> wrote:
> 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?
>
>
Oh, and turn synchronous_commit off too.
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Szymon Guz | 2010-11-05 11:23:36 | Re: Running PostgreSQL as fast as possible no matter the consequences |
| Previous Message | Thom Brown | 2010-11-05 11:14:43 | Re: Running PostgreSQL as fast as possible no matter the consequences |