X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 1B782D1B9AA for ; Wed, 7 Apr 2004 14:22:23 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 10415-01 for ; Wed, 7 Apr 2004 14:22:21 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 4EA51D1B989 for ; Wed, 7 Apr 2004 14:22:20 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i37HMKcX022308; Wed, 7 Apr 2004 13:22:20 -0400 (EDT) To: "Tom Bakken" Cc: pgsql-admin@postgresql.org Subject: Re: Out of space In-reply-to: <000a01c41cbd$3e916850$770e9dc7@agwest.one.usda.gov> References: <000a01c41cbd$3e916850$770e9dc7@agwest.one.usda.gov> Comments: In-reply-to "Tom Bakken" message dated "Wed, 07 Apr 2004 11:27:39 -0500" Date: Wed, 07 Apr 2004 13:22:20 -0400 Message-ID: <22307.1081358540@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/115 X-Sequence-Number: 13088 "Tom Bakken" writes: > I've been running a postgres for 2 or 3 years without a problem. This > morning my disk space for the database filled up. I need to know what > transaction/log files I can truncate or delete without compromising the > system. These files are located under /var/lib/pgsql/data/ I wouldn't recommend deleting *any* files manually --- unless you find core files or old files underneath a pgsql_tmp subdirectory. Those you could zap at little risk. The best approach is to free up a small amount of space elsewhere, enough so you can get through a CHECKPOINT without failing. The checkpoint will hopefully free up some space in pg_xlog. After that you can look at dropping tables you don't need any more, VACUUM FULL, etc. regards, tom lane