X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C77F13A5784 for ; Mon, 10 Jan 2005 23:00:40 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 53468-08 for ; Mon, 10 Jan 2005 23:00:35 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 1FCCB3A57C8 for ; Mon, 10 Jan 2005 23:00:36 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j0AN0WRR009544; Mon, 10 Jan 2005 18:00:32 -0500 (EST) To: "Lee Wu" Cc: pgsql-admin@postgresql.org Subject: Re: Vacuum full - disk space eaten by WAL logfiles In-reply-to: References: Comments: In-reply-to "Lee Wu" message dated "Mon, 10 Jan 2005 14:52:24 -0700" Date: Mon, 10 Jan 2005 18:00:32 -0500 Message-ID: <9543.1105398032@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.003 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/61 X-Sequence-Number: 15920 "Lee Wu" writes: > 3. It is "vacuum full" as shown: Hmm. I'm not able to replicate any such problem here: AFAICS, checkpoints go through to completion just fine while a VACUUM is running. This might mean that the problem was fixed between 7.3.2 and 7.3.8 (though I see nothing relevant-looking in the changelog). Or it might mean that you've not given enough information to let someone else duplicate the problem. What else is going on in parallel with the VACUUM? (We know at least some COPY operations...) Again, it would be useful to know whether the checkpoint process is making progress or not. regards, tom lane