Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>   
>> ! 		print O "#define RELSEG_SIZE ",
>> ! 			(1024 / $self->{options}->{blocksize}) * 
>> ! 				$self->{options}->{segsize} * 1024, "\n";
>>     
>
> This doesn't look quite right; unless the arithmetic is being done in
> floating point?  I had it like this in configure.in:
>
> RELSEG_SIZE=`expr '(' 1024 '*' ${segsize} / ${blocksize} ')' '*' 1024`
>   

blocksize is one of (1,2,4,8,16,32)  so it should always be a factor of 
1024 unless my arithmetic is awry. I did it that way because I dislike 
expressions with  unbracketed mixed operations - they make me think too 
much.

> Also it looks like you missed adding segsize to the config.pl comments.
>
> 			
>   

That's deliberate - we are currently only allowing a value of 1 here, so 
I don't see any point in putting it in the sample config file, even as a 
comment. When we enable other seg sizes we can add it to the sample file.

cheers

andrew

In response to

• Re: [COMMITTERS] pgsql: Sigh ... at 2008-05-02 22:28:41 from Tom Lane

Responses

• Re: [COMMITTERS] pgsql: Sigh ... at 2008-05-02 23:23:34 from Tom Lane

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2008-05-02 23:19:00
	Subject: Re: ecpg localization
Previous:	From: Tom Lane	Date: 2008-05-02 22:28:41
	Subject: Re: [COMMITTERS] pgsql: Sigh ...

pgsql-committers by date

Next:	From: Tom Lane	Date: 2008-05-02 23:23:34
	Subject: Re: [COMMITTERS] pgsql: Sigh ...
Previous:	From: Tom Lane	Date: 2008-05-02 22:50:21
	Subject: pgsql: Update documentation for psql relation-size-in-\dt+ patch.

pgsql-patches by date

Next:	From: Tom Lane	Date: 2008-05-02 23:05:52
	Subject: Re: plpgsql CASE statement - last version
Previous:	From: Tom Lane	Date: 2008-05-02 22:28:41
	Subject: Re: [COMMITTERS] pgsql: Sigh ...