From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Jacky Leng <lengjianquan(at)163(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Has anybody think about changing BLCKSZ to an option of initdb? |
Date: | 2009-03-14 15:51:17 |
Message-ID: | 1237045877.29094.5.camel@jd-laptop.pragmaticzealot.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, 2009-03-14 at 11:47 -0400, Tom Lane wrote:
> Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> > So has anyone here done any experiments with live systems with different block
> > sizes? What were your experiences?
>
> That should really have been the *first* question. We are not going to
> make this a tunable unless there is some pretty strong evidence that
> it's worth twiddling. Aside from the implementation costs of making
> it variable, there is the oft repeated refrain that Postgres has too
> many configuration knobs already.
Well that "too many knobs" argument doesn't apply to this scenario etc.
Anyone who is making use of these need those knobs. It is the other 98%
that really just need to crank up half a dozen parameters and PostgreSQL
is blazing fast for them that make that argument (which is why we should
rip everything out of the postgresql.conf).
Joshua D. Drake
>
> regards, tom lane
>
--
PostgreSQL - XMPP: jdrake(at)jabber(dot)postgresql(dot)org
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-03-14 16:25:23 | Re: Has anybody think about changing BLCKSZ to an option of initdb? |
Previous Message | Tom Lane | 2009-03-14 15:47:24 | Re: Has anybody think about changing BLCKSZ to an option of initdb? |