You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@manifoldcf.apache.org by Marcello Lorenzi <ml...@sorint.it> on 2013/11/12 16:12:07 UTC
Manifold and pg_xlog data
Hi,
we have configured PostgreSQL as described by Performance page on
ManifoldCF website but after a large number of crawling (intensive sets
of data), we have noticed that the directory pg_xlog uses more than 3 GB
of space.
This directory contains the WAL transaction file and the size of this is
limited by the directive checkpoint_segments and in the document is
written to set this value to 300 with a final size of 5 GB.
Why this parameter is too high?
Thanks,
Marcello
Re: Manifold and pg_xlog data
Posted by Karl Wright <da...@gmail.com>.
Hi Marcello,
The person who came up with the recommendations in the Performance page was
not me, but rather a contributor who had all the hardware and database
expertise needed to tune the version of PostgreSQL that was current at that
time. Perhaps he felt that PostgreSQL performs better with a longer
checkpoint interval, but I don't know that for certain. It is possible,
therefore, that your mileage may vary. In any case, there is no
*intrinsic* reason that you could not experiment with changing the numbers
and explore how the database performs.
Karl
On Tue, Nov 12, 2013 at 10:12 AM, Marcello Lorenzi <ml...@sorint.it>wrote:
> Hi,
> we have configured PostgreSQL as described by Performance page on
> ManifoldCF website but after a large number of crawling (intensive sets of
> data), we have noticed that the directory pg_xlog uses more than 3 GB of
> space.
>
> This directory contains the WAL transaction file and the size of this is
> limited by the directive checkpoint_segments and in the document is written
> to set this value to 300 with a final size of 5 GB.
>
> Why this parameter is too high?
>
> Thanks,
> Marcello
>