From d61eecb5a17d1b9373ca75fb4d6de4e35ba3f640 Mon Sep 17 00:00:00 2001
From: Andrew Dunstan
Date: Sat, 3 May 2008 00:24:06 +0000
Subject: Provide for MSVC config equivalents of recently added configure
 options. Remove any hardcoding of those options. Along the way, reorder the
 expression used to calculate RELSEG_SIZE to make it slightly clearer. For now
 wal_segsize is only allowed to have a value of 1 on Windows - we can relax
 that when we get full large file support in the backend.

---
 configure.in | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to 'configure.in')

diff --git a/configure.in b/configure.in
index 9925389a472..b8f83960308 100644
--- a/configure.in
+++ b/configure.in
@@ -1,5 +1,5 @@
 dnl Process this file with autoconf to produce a configure script.
-dnl $PostgreSQL: pgsql/configure.in,v 1.559 2008/05/02 19:52:37 tgl Exp $
+dnl $PostgreSQL: pgsql/configure.in,v 1.560 2008/05/03 00:24:05 adunstan Exp $
 dnl
 dnl Developers, please strive to achieve this order:
 dnl
@@ -257,7 +257,8 @@ PGAC_ARG_REQ(with, segsize, [  --with-segsize=SEGSIZE  set table segment size in
              [segsize=$withval],
              [segsize=1])
 # this expression is set up to avoid unnecessary integer overflow
-RELSEG_SIZE=`expr '(' 1024 '*' ${segsize} / ${blocksize} ')' '*' 1024`
+# blocksize is already guaranteed to be a factor of 1024
+RELSEG_SIZE=`expr '(' 1024 / ${blocksize} ')' '*' ${segsize} '*' 1024`
 test $? -eq 0 || exit 1
 AC_MSG_RESULT([${segsize}GB])
 
-- 
cgit v1.2.3