Postgres Pro
Downloads
Home   >   mailing lists

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

From A B
Subject Re: Running PostgreSQL as fast as possible no matter the consequences
Date
Msg-id AANLkTin+ZRe5mEOj72ga8xOfbULpYn6kwH4hy_JCBYm2@mail.gmail.com
Whole thread Raw
In response to Re: Running PostgreSQL as fast as possible no matter the consequences  (Szymon Guz <mabewlun@gmail.com>)
Responses Re: Running PostgreSQL as fast as possible no matter the consequences  (Marti Raudsepp <marti@juffo.org>)
Re: Running PostgreSQL as fast as possible no matter the consequences  (Craig Ringer <craig@postnewspapers.com.au>)
Re: Running PostgreSQL as fast as possible no matter the consequences  ("Lello, Nick" <nick.lello@rentrakmail.com>)
List pgsql-performance
Tree view 
>> 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.

pgsql-performance by date:

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