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

From: A B <gentosaker(at)gmail(dot)com>
To: Szymon Guz <mabewlun(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:32:39
Message-ID: AANLkTin+ZRe5mEOj72ga8xOfbULpYn6kwH4hy_JCBYm2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

>> 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?
>>
>
>
> I'm just curious, what do you need that for?
>
> regards
> Szymon

I was just thinking about the case where I will have almost 100%
selects, but still needs something better than a plain key-value
storage so I can do some sql queries.
The server will just boot, load data, run, hopefully not crash but if
it would, just start over with load and run.

In response to

Responses

Browse pgsql-performance by date

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