I'll check into the temp files and the like in a bit -- the output from version() says:
PostgreSQL 7.4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk)
(1 row)
so I am not sure if this 7.4.2 -- I have some documentation though that says it is 7.4.2 so I think this beast may be
ofthat flavor.
'
Thanks,
Greg
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Mon 1/2/2006 9:45 AM
To: Gregory S. Williamson
Cc: Jeff Frost; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] full data disk -- any chance of recovery
"Gregory S. Williamson" <gsw@globexplorer.com> writes:
> 2006-01-02 00:30:01 LOG: could not close temporary statistics file
"/data/postgres/gex_runtime/global/pgstat.tmp.1453":No space left on device
> 2006-01-02 00:33:54 ERROR: could not access status of transaction 0
> DETAIL: could not write to file "/data/postgres/gex_runtime/pg_clog/0AFA" at offset 196608: No space left on device
Just kill -9 all the postgres processes; everything you need should be
safely down in the WAL files.
You might not have to move pg_xlog --- the first thing to do is see
if there are any large temp files hanging about in the pgsql_tmp
subdirectories. Anything you see in there can be shot on sight once
the postmaster is stopped (actually, recent versions of the postmaster
will do it for you on restart, but don't remember about 7.4).
Which PG release is this exactly (7.4.what)? This misbehavior reminds
me of a bug that we fixed in 7.4.2.
regards, tom lane
!DSPAM:43b9668499131348188260!