From: | "Tom Bakken" <tom(dot)bakken(at)tx(dot)usda(dot)gov> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Out of space |
Date: | 2004-04-07 19:28:40 |
Message-ID: | 001801c41cd6$8888eaf0$770e9dc7@agwest.one.usda.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Tom,
I'm not finding any mention of CHECKPOINT in my references. Is that
something from a version newer than 7.1.2?
Tom Bakken
Information Resource Manager
Texas USDA, Rural Development
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Wednesday, April 07, 2004 12:22 PM
To: Tom Bakken
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Out of space
"Tom Bakken" <tom(dot)bakken(at)tx(dot)usda(dot)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
Attachment | Content-Type | Size |
---|---|---|
Tom.Bakken@tx.usda.gov.vcf | text/x-vcard | 447 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Bakken | 2004-04-07 19:42:35 | Re: Out of space |
Previous Message | Tom Bakken | 2004-04-07 19:23:59 | Re: Out of space |