From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Michael Holt <michael(at)aers(dot)ca> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Seems like a large amount of xlog files |
Date: | 2011-05-26 01:42:08 |
Message-ID: | BANLkTi=5k=cgCVAaB8M4gj_eJSTTAuctLA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
CC to pgsql-admin(at)postgresql(dot)org
On Wed, May 25, 2011 at 5:10 PM, Michael Holt <michael(at)aers(dot)ca> wrote:
> archive_timeout is not set. The default is to have it off right?
Yes.
My another guess is that those many files were generated by
initial data load and have remained up to now. No?
Anyway, you can check whether your system is still generating
so many WAL files now, by periodically calling
pg_current_xlog_location(). This function returns the current
WAL write location, so if the rate of increase of that location
is small, you don't need to worry about the number of files.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2011-05-26 05:05:53 | Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum |
Previous Message | Robert Haas | 2011-05-25 23:11:31 | Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum |