| From: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
|---|---|
| To: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
| Cc: | "Aurangzeb M(dot) Agha" <ama-list(at)mltp(dot)com>, Richard Huxton <dev(at)archonet(dot)com>, PostgreSQL General List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: no space left on device |
| Date: | 2004-01-09 23:46:11 |
| Message-ID: | 3FFF3D43.6030201@paradise.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I would suspect some *other* service is using the 4G for transient
storage every now and again, and it just so happens that Pg is getting
tripped up.
What else does this machine run ?
regards
Mark
Nigel J. Andrews wrote:
>On Fri, 9 Jan 2004, Aurangzeb M. Agha wrote:
>
>
>
>>Here's the output of "df -m":
>>
>>[postgres - DB]$ df -m .
>>Filesystem 1M-blocks Used Available Use% Mounted on
>>- 63328 55308 4803 93% /
>>
>>
>>
>
>But your du, below, of the postgres data directory shows 53MB in use. That's an
>order of magnitude smaller than the 55GB the above appears to be saying is used
>in the db.
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2004-01-10 00:20:11 | Re: ERROR: Cannot insert a duplicate key into unique index pg_class_relname_nsp_index |
| Previous Message | Tom Lane | 2004-01-09 23:35:29 | Re: no space left on device |