From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tom Bakken <tom.bakken@tx.usda.gov>
Cc: pgsql-admin@postgresql.org
Subject: Re: Out of space
Date: Wed, 07 Apr 2004 13:22:20 -0400
Message-ID: <22307.1081358540@sss.pgh.pa.us> (raw)
In-Reply-To: <000a01c41cbd$3e916850$770e9dc7@agwest.one.usda.gov>
References: <000a01c41cbd$3e916850$770e9dc7@agwest.one.usda.gov>
"Tom Bakken" <tom.bakken@tx.usda.gov> 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
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, tom.bakken@tx.usda.gov
Subject: Re: Out of space
In-Reply-To: <22307.1081358540@sss.pgh.pa.us>
References: <000a01c41cbd$3e916850$770e9dc7@agwest.one.usda.gov> <22307.1081358540@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