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 B34C63A5599 for ; Mon, 10 Jan 2005 21:27:09 +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 42726-10 for ; Mon, 10 Jan 2005 21:26:55 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id DD7B13A57CD for ; Mon, 10 Jan 2005 21:26:56 +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 j0ALQqSt003251; Mon, 10 Jan 2005 16:26:53 -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 10:45:15 -0700" Date: Mon, 10 Jan 2005 16:26:52 -0500 Message-ID: <3250.1105392412@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/59 X-Sequence-Number: 15918 "Lee Wu" writes: > When we do weekly "vacuum full", PG uses all space and causes PG down. This implies that checkpoints aren't completing for some reason. If they were, they'd be recycling WAL space. I'm not aware of any problems in 7.3 that would block a checkpoint indefinitely, but we have seen cases where it just took too darn long to do the checkpoint --- implying either a ridiculously large shared_buffers setting, or a drastic shortage of I/O bandwidth. You might want to try strace'ing the checkpoint process to see if it seems to be making progress or not. Also, are you certain that this is happening during a VACUUM? The log messages you show refer to COPY commands. > PostgreSQL 7.3.2 on i686-pc-linux-gnu, compiled by GCC 2.96 Are you aware of the number and significance of post-7.3.2 bug fixes in the 7.3 branch? You really ought to be on 7.3.8, if you can't afford to migrate to 7.4 right now. regards, tom lane