Tom,
Doh!! I created that log file and let it get out of hand.
OK, it's truncated and now I've got plenty of space, but it's still
complaining that it can't find the xlogtemp.1405:
DEBUG: database system was shut down at 2004-04-07 12:14:38 CDT
DEBUG: CheckPoint record at (1, 516646732)
DEBUG: Redo record at (1, 516646732); Undo record at (0, 0); Shutdown TRUE
DEBUG: NextTransactionId: 28728439; NextOid: 9098648
FATAL 2: ZeroFill(/var/lib/pgsql/data/pg_xlog/xlogtemp.1405) failed: No
such file or directory
/usr/bin/postmaster: Startup proc 1405 exited with status 512 - abort
Again, I know I didn't delete it, but regardless, I'm unsure where to go
from here.
Thanks for all your help. I hope we're close to a fix.
Tom Bakken
Information Resource Manager
Texas USDA, Rural Development
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Wednesday, April 07, 2004 3:57 PM
To: Tom Bakken
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Out of space
"Tom Bakken" <tom.bakken@tx.usda.gov> writes:
> Here's the situation:
> [root@linux04 init.d]# cd /var/lib/pgsql/data/
> [root@linux04 data]# ls -l
> total 1494316
> -rw------- 1 postgres postgres 4 Jun 21 2001 PG_VERSION
> drwx------ 6 postgres postgres 4096 Sep 17 2003 base
> drwx------ 2 postgres postgres 4096 Oct 27 13:40 global
> -rw-r--r-- 1 root root 7640 Jun 29 2001 h
> -rw------- 1 postgres postgres 9070 Mar 2 10:56 pg_hba.conf
> -rw------- 1 postgres postgres 1118 Jun 21 2001 pg_ident.conf
> -rw------- 1 postgres postgres 1528630320 Apr 7 14:26 pg_log
> drwx------ 2 postgres postgres 4096 Apr 7 14:26 pg_xlog
> -rw------- 1 postgres postgres 3137 Jun 21 2001 postgresql.conf
> -rw------- 1 postgres postgres 52 Apr 7 14:26 postmaster.opts
> [root@linux04 data]# ls -l pg_xlog/
> total 16404
> -rw------- 1 postgres postgres 16777216 Apr 7 12:14 000000010000001E
> I do have a limited amount of space in the partition but I'd like to get =
> rid of more. Just not sure what to delete if anything.
Hm, what is that pg_log file? It's not part of the normal Postgres
fileset. Is it perhaps just the postmaster's stderr output? If so,
you're in luck: truncate that as you see fit, and you'll have some
breathing room.
regards, tom lane