Received: from maia.hub.org (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 45CA16333FC
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed,  3 Mar 2010 14:01:24 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia,
	port 10024) with ESMTP id 64297-06 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed,  3 Mar 2010 18:01:13 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-iw0-f187.google.com (mail-iw0-f187.google.com
	[209.85.223.187])
	by mail.postgresql.org (Postfix) with ESMTP id 26F306336DF
	for <pgsql-admin@postgresql.org>; Wed,  3 Mar 2010 14:01:09 -0400 (AST)
Received: by iwn17 with SMTP id 17so1580009iwn.19
	for <pgsql-admin@postgresql.org>; Wed, 03 Mar 2010 10:01:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:date:message-id:subject:from:to:content-type;
	bh=faCt9GTbKmO9zHzvHHESN7CfOAcC5xJBfVmGz4BHeho=;
	b=irsHqb9mG4gHsWhJCCzf95NmQKhz+i+pdaXk052ZSSsPEqj6X104LrWKSOD7Ajiy2O
	BQpJ+H+9szMlhgs05bWhTfkyhwYIJRa2e7MnhdSkOlENyDRXTjS6p8WAvY2LtFxxRvLB
	SrU1jbHrVcXQobqlElc0PWh651UvL32nRwOQU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	b=LC5IuRZknaXtkvjXRoUC+Bbx/JaTFVoAMiwZBab+4aRbAU9MB/dwAxqm5T1YIRASdz
	qgbPo5RKbFJamhSMm81M/io8m8mPjFPhA7Qop2wMHYy88U0LYOV25B3twagIA6JNuITf
	INb7/ScCRVQtQDI7K+b3X0e6J8Q6gnBmyZ6K0=
MIME-Version: 1.0
Received: by 10.231.169.71 with SMTP id x7mr341811iby.18.1267639268257; Wed,
	03 Mar 2010 10:01:08 -0800 (PST)
In-Reply-To: <f3e51c11003030932g4a12e1c7u4d5852f0b7cde0e8@mail.gmail.com>
References: <f3e51c11003030932g4a12e1c7u4d5852f0b7cde0e8@mail.gmail.com>
Date: Wed, 3 Mar 2010 13:01:08 -0500
Message-ID: <f3e51c11003031001p2812f739ifb766aec3e017d5a@mail.gmail.com>
Subject: Fwd: --with-wal-segsize in-effective?
From: Dhimant Patel <drp4kri@gmail.com>
To: pgsql-admin@postgresql.org
Content-Type: multipart/alternative; boundary=0016369205f649b2d00480e9447d
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-2.598 tagged_above=-10 required=5
	tests=BAYES_00=-2.599, HTML_MESSAGE=0.001
X-Spam-Level: 
X-Archive-Number: 201003/33
X-Sequence-Number: 33832

--0016369205f649b2d00480e9447d
Content-Type: text/plain; charset=ISO-8859-1

To investigate this further I worked on the 8.4.2 source code and it allows
to set the xlog segment size but still does not follow what documentation
implies - unless I am wrong.

--with-wal-segsize=2 as per documentation should give me 4MB size segment, I
am getting it of 2MB.

Thanks,
DP.

---------- Forwarded message ----------
From: Dhimant Patel <drp4kri@gmail.com>
Date: Wed, Mar 3, 2010 at 12:32 PM
Subject: --with-wal-segsize in-effective?
To: pgsql-admin@postgresql.org


Hi All,

I am working with latest source downloaded from postgres org site.
I compiled and installed the source with --with-wal-segsize=2, assuming it
should give me 4MB size xlog files. (As per the documentation it is a power
of 2 value.)

During the compilation the configure script spitted out "checking for WAL
segment size... 2MB"  - so something was off - and I could not imagine what
it is. After successful install and creating database, I still got 16MB
files in my pg_xlog directory. That's too bad. I can not seem to be able to
follow.

I thought it time to turn on archive anyway. I got 16MB files in my archive
location!


So what am I doing wrong?

Please help.

-DP.

--0016369205f649b2d00480e9447d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

To investigate this further I worked on the 8.4.2 source code and it allows=
 to set the xlog segment size but still does not follow what documentation =
implies - unless I am wrong.<br><br>--with-wal-segsize=3D2 as per documenta=
tion should give me 4MB size segment, I am getting it of 2MB.<br>
<br>Thanks,<br>DP.<br><br><div class=3D"gmail_quote">---------- Forwarded m=
essage ----------<br>From: <b class=3D"gmail_sendername">Dhimant Patel</b> =
<span dir=3D"ltr">&lt;<a href=3D"mailto:drp4kri@gmail.com">drp4kri@gmail.co=
m</a>&gt;</span><br>
Date: Wed, Mar 3, 2010 at 12:32 PM<br>Subject: --with-wal-segsize in-effect=
ive?<br>To: <a href=3D"mailto:pgsql-admin@postgresql.org">pgsql-admin@postg=
resql.org</a><br><br><br>Hi All,<br><br>I am working with latest source dow=
nloaded from postgres org site.<br>
I compiled and installed the source with --with-wal-segsize=3D2, assuming i=
t should give me 4MB size xlog files. (As per the documentation it is a pow=
er of 2 value.) <br>
<br>During the compilation the configure script spitted out &quot;checking =
for WAL segment size... 2MB&quot;=A0 - so something was off - and I could n=
ot imagine what it is. After successful install and creating database, I st=
ill got 16MB files in my pg_xlog directory. That&#39;s too bad. I can not s=
eem to be able to follow. <br>

<br>I thought it time to turn on archive anyway. I got 16MB files in my arc=
hive location!<br><br><br>So what am I doing wrong?<br><br>Please help.<br>=
<font color=3D"#888888"><br>-DP.<br>
</font></div><br>

--0016369205f649b2d00480e9447d--