From: Euler Taveira de Oliveira <euler@timbira.com>
To: Tech Madhu <technimadhu@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: pg_xlog size
Date: Wed, 16 Mar 2011 14:27:36 -0300
Message-ID: <4D80F308.3050207@timbira.com> (raw)
In-Reply-To: <AANLkTik6ud2NrbLoLYCOkKW0eFva5n4LKeTYX93i+Dqt@mail.gmail.com>
References: <AANLkTik6ud2NrbLoLYCOkKW0eFva5n4LKeTYX93i+Dqt@mail.gmail.com>
Em 15-03-2011 12:09, Tech Madhu escreveu:
[This is not a performance question, next time post at the appropriate list,
that is -general]
> Everything works fine (w.r.t replication), but the pg_xlog size grows
> continuously, though i had no operations going on. Also the archiving to
> the other side filled up the other side FS.
> ls -l /var/postgres/data/pg_xlog | wc -l
> 103
Did you consider using pg_archivecleanup [1]?
> At start, there were only 15 files. The max_wal_segments is 32, but not
> sure why iam seeing 103 files. Also the archiving dir size doubled
> (w.r.t number of files archived). and filled up the filesystem.
> I manually logged into postgres and run checkpoint; did not see any file
> reduction
>
max_wal_segments [2] is *not* related to archiving activity.
[1] http://www.postgresql.org/docs/9.0/static/pgarchivecleanup.html
[2]
http://www.postgresql.org/docs/9.0/static/runtime-config-wal.html#GUC-WAL-KEEP-SEGMENTS
--
Euler Taveira de Oliveira
http://www.timbira.com/
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-performance@postgresql.org
Cc: euler@timbira.com, technimadhu@gmail.com
Subject: Re: pg_xlog size
In-Reply-To: <4D80F308.3050207@timbira.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