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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <stark(at)enterprisedb(dot)com>
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 13:13:33
Message-ID: 26451.1236777213@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg Stark <stark(at)enterprisedb(dot)com> writes:
> 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.

Exactly, and we rely on them being constants, eg to size arrays.

There's no free lunch, and in this particular case there is no evidence
whatsoever that it'd be worth the trouble to support run-time-variable
BLCKSZ.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

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