From: | Thom Brown <thombrown(at)gmail(dot)com> |
---|---|
To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
Cc: | PGSQL Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Reducing excess files in pg_xlog |
Date: | 2010-03-22 16:37:01 |
Message-ID: | bddc86151003220937j63a1cbact337a76db86b3408d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 22 March 2010 16:06, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> Thom Brown wrote:
>
>> I noticed there's 66 files in my pg_xlog directory. I changed my
>> checkpoint_segments from 32 to 3 as I noticed it was too high, restarted
>> PosgreSQL, but there are still 66 files in that directory and they're taking
>> up about 1.1G.
>> How can I get this list of files down?
>>
>
> A checkpoint after there's been some write activity in the database should
> reduce this down to a reasonable number. If the system has been idle since
> the last checkpoint, it doesn't do anything when you ask for another one,
> which includes skipping this cleanup; that may be why you haven't seen it
> drop yet.
>
> I'm assuming you don't have WAL shipping turned on by setting
> archive_command. There can also be an excess of these segments that can't
> be cleaned up if your archiving scheme fails.
>
>
Hi Greg,
You're right, I don't have the archiving enabled. All options are commented
out.
I've just forced a new WAL file by writing lots of stuff to a table, then
deleting it. It appears to be recyling the filenames now. The latest files
end in DD and DE, and the earliest is DF. Presumably these will slowly get
eaten up until it's just down to the 3 files I've configured it for?
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-03-22 16:47:44 | Re: Reducing excess files in pg_xlog |
Previous Message | Tom Lane | 2010-03-22 16:36:59 | Re: strange |