From: Tom Lane <tgl@sss.pgh.pa.us>
To: Lee Wu <Lwu@mxlogic.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Vacuum full - disk space eaten by WAL logfiles
Date: Tue, 11 Jan 2005 14:59:55 -0500
Message-ID: <3615.1105473595@sss.pgh.pa.us> (raw)
In-Reply-To: <ECAB83AA52BCC043A0E24BBC000010241114E7@mxhq-exch.corp.mxlogic.com>
References: <ECAB83AA52BCC043A0E24BBC000010241114E7@mxhq-exch.corp.mxlogic.com>
"Lee Wu" <Lwu@mxlogic.com> writes:
> Here is postgres log from 20:17:42 to 20:25:35.
> I did NOT removing anything except hostname and table names.
Hmm. That shows the checkpoint process (8213) in a tight loop removing
unwanted XLOG files. But apparently it is being starved for cycles ---
look at the gaps between log entries. There's no problem with removing
eight per second at 20:17:46, but after that there are periods of 10 to
20 seconds where it doesn't get to run at all. It really should have
finished this phase in a few seconds, but instead it's still trying to
do the removal seven minutes later when the COPY process fails.
Apparently the COPY and VACUUM and whatever else is going on are able
to create/use XLOG files faster than the checkpoint process can remove
them. Which makes no sense.
I think there is something fairly odd about either your kernel scheduler
or your filesystem. What sort of platform is this anyway?
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, Lwu@mxlogic.com
Subject: Re: Vacuum full - disk space eaten by WAL logfiles
In-Reply-To: <3615.1105473595@sss.pgh.pa.us>
References: <ECAB83AA52BCC043A0E24BBC000010241114E7@mxhq-exch.corp.mxlogic.com> <3615.1105473595@sss.pgh.pa.us>
* 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