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

From Guillaume Cottenceau
Subject Re: Running PostgreSQL as fast as possible no matter the consequences
Date
Msg-id 87hbfwvupx.fsf@meuh.mnc.lan
Whole thread Raw
In response to Re: Running PostgreSQL as fast as possible no matter the consequences  (Marti Raudsepp <marti@juffo.org>)
Responses Re: Running PostgreSQL as fast as possible no matter the consequences  (Jon Nelson <jnelson+pgsql@jamponi.net>)
List pgsql-performance
Marti Raudsepp <marti 'at' juffo.org> writes:

> On Fri, Nov 5, 2010 at 13:32, A B <gentosaker@gmail.com> wrote:
>> 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.
>
> If you want fast read queries then changing
> fsync/full_page_writes/synchronous_commit won't help you.

That illustrates how knowing the reasoning of this particular
requests makes new suggestions worthwhile, while previous ones
are now seen as useless.

--
Guillaume Cottenceau

pgsql-performance by date:

Previous
From: Guillaume Cottenceau
Date:
Subject: Re: Running PostgreSQL as fast as possible no matter the consequences
Next
From: Jon Nelson
Date:
Subject: Re: Running PostgreSQL as fast as possible no matter the consequences