Re: Growing pg_xlog

From: Florian Weimer <fw(at)deneb(dot)enyo(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Growing pg_xlog
Date: 2003-07-14 17:12:16
Message-ID: 20030714171216.GA68252@ext1.enyo.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Mon, Jul 14, 2003 at 12:55:19PM -0400, Tom Lane wrote:

> Florian Weimer <fw(at)deneb(dot)enyo(dot)de> writes:
> > I seem to have some obscure problem with the WAL logs (AFAIK that's what
> > is stored in the pg_xlog directory):
>
> > 63G /var/lib/postgres/data/pg_xlog
>
> > This is a bit too much wasted space for my taste. 8-/
>
> The only theory that comes to mind is that the automatically issued
> checkpoint operations are failing before they get to the stage of
> truncating the WAL. Is there anything suspicious looking in the
> postmaster log?

No, I'm afraid. However, the checkpoint subprocess was stuck in the "T"
state (meaning that it had received SIGSTOP). 8-/

> You could also try a manual CHECKPOINT and see if it fails.

Sending SIGCONT, restarting the database and issuing a CHECKPOINT
command seems to have fixed it (CHECKPOINT removed the gigabytes at an
amazing rate 8-).

Thanks for pushing me into the right direction.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Chris Miles 2003-07-14 19:15:15 PostgreSQL performance experts in London
Previous Message Tom Lane 2003-07-14 16:55:19 Re: Growing pg_xlog