Re: Has anybody think about changing BLCKSZ to an option of initdb?

From: Greg Stark <stark(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-11 12:57:42
Message-ID: 4136ffa0903110557l67bcfbc0jfb4a990ce33cfdc@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 11, 2009 at 12:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> And there seems nothing diffcult to implement this. Is that true?
>
> No.

Eh? There's nothing difficult in implementing it.

But there are a lot of other constants dependant on this value which
are currently compile-time constants. The only downside I'm aware of
is that with this change they become dynamically calculated values
which might have a cpu cost since they'll be recalculated quite often.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2009-03-11 13:02:45 Re: gcc: why optimize for size flag is not the default
Previous Message Simon Riggs 2009-03-11 12:56:11 Re: idea, proposal: only preloadable libraries (conditional load)