From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Richard Boyes <r(dot)boyes(at)auckland(dot)ac(dot)nz> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Temporary sorting space |
Date: | 2001-03-07 04:12:58 |
Message-ID: | 8392.983938378@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Richard Boyes <r(dot)boyes(at)auckland(dot)ac(dot)nz> writes:
> Inside the $PGDATA/base/thedatabase I came across a rather
> large file called pg_sorttemp28193.0 (~ 587 MB). Our datbase
> is not anywhere near this large, so I can only guess this was
> a query gone awry that needed a large amount of sorting space.
> Around the time this file was created the database server
> also crashed, I'm wondering if this was a cause of it
> (the server crashed due to a memory problem). Could that be possible ?
Possibly, but this is not a lot of evidence. Can you provide any
log file entries, core dump backtraces, etc?
> Also, would I now be safe in removing this file ?
If there's not currently a backend with PID 28193, then that's a
dead file. Zap away.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | will trillich | 2001-03-07 05:26:25 | need general optimization advice |
Previous Message | Tom Lane | 2001-03-07 04:04:55 | Re: vacuum analyze returns "OID IS INVALID. TUPGONE 1" on pg_language |