From: Guillaume Cottenceau <gc@mnc.ch>
To: Marti Raudsepp <marti@juffo.org>
Cc: A B <gentosaker@gmail.com>
Cc: Szymon Guz <mabewlun@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Running PostgreSQL as fast as possible no matter the consequences
Date: Fri, 05 Nov 2010 13:08:26 +0100
Message-ID: <87hbfwvupx.fsf@meuh.mnc.lan> (raw)
In-Reply-To: <AANLkTi=9CL-O=D_eiCxx7R=1zkGhimAotnGgB_WsvC2-@mail.gmail.com>
References: <AANLkTimcUYuutQeThCaP-077reGYWwdq-ssKwbPne8TO@mail.gmail.com>
<AANLkTikVBTRkZCTiqzwRYemJhHLvwwrnA1WHguBpc5Qp@mail.gmail.com>
<AANLkTin+ZRe5mEOj72ga8xOfbULpYn6kwH4hy_JCBYm2@mail.gmail.com>
<AANLkTi=9CL-O=D_eiCxx7R=1zkGhimAotnGgB_WsvC2-@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gc@mnc.ch, marti@juffo.org, gentosaker@gmail.com, mabewlun@gmail.com
Subject: Re: Running PostgreSQL as fast as possible no matter the consequences
In-Reply-To: <87hbfwvupx.fsf@meuh.mnc.lan>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox