| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | ama-list(at)mltp(dot)com |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL General List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: no space left on device |
| Date: | 2004-01-09 23:35:29 |
| Message-ID: | 27167.1073691329@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Aurangzeb M. Agha" <ama-list(at)mltp(dot)com> writes:
> Re inodes, how can I check this?
"df -i" should help.
> But why would this be? Is Postgres
> sucking up inodes just sitting there as a read-only DB?
I think you have missed the point here. Postgres is using 0.1 percent
of your disk; whatever is eating disk space or inodes is somewhere in
the 92.9% of the disk that you have not told us about. You are focusing
on killing the messenger instead of finding the true source of the
problem.
You should also check into the per-user-quota possibility.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2004-01-09 23:46:11 | Re: no space left on device |
| Previous Message | Dennis Björklund | 2004-01-09 23:30:51 | Re: no space left on device |