From: Dhimant Patel <drp4kri@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Fwd: --with-wal-segsize in-effective?
Date: Wed, 3 Mar 2010 13:01:08 -0500
Message-ID: <f3e51c11003031001p2812f739ifb766aec3e017d5a@mail.gmail.com> (raw)
In-Reply-To: <f3e51c11003030932g4a12e1c7u4d5852f0b7cde0e8@mail.gmail.com>
References: <f3e51c11003030932g4a12e1c7u4d5852f0b7cde0e8@mail.gmail.com>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: drp4kri@gmail.com
Subject: Re: Fwd: --with-wal-segsize in-effective?
In-Reply-To: <f3e51c11003031001p2812f739ifb766aec3e017d5a@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox