Re: Has anybody think about changing BLCKSZ to an option of initdb? - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Has anybody think about changing BLCKSZ to an option of initdb?
Date
Msg-id 4136ffa0903110557l67bcfbc0jfb4a990ce33cfdc@mail.gmail.com
Whole thread Raw
In response to Re: Has anybody think about changing BLCKSZ to an option of initdb?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Has anybody think about changing BLCKSZ to an option of initdb?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Mar 11, 2009 at 12:38 PM, Tom Lane <tgl@sss.pgh.pa.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


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: idea, proposal: only preloadable libraries (conditional load)
Next
From: Greg Stark
Date:
Subject: Re: gcc: why optimize for size flag is not the default