Hi,
Sorry for replying to myself, but I had to point out that:
I'm guessing that the new table/index files created during the CLUSTER
didn't get released after the PANIC. Look for files that are not
referenced by any relfilenode value in pg_class.
Using the oid2name tool I get this:
[...]
I suspec
Hi Tom,
2005-01-15 15:17:46 [30605] PANIC: PANIC: could not write to file
"/var/lib/pgsql/data/pg_xlog/xlogtemp.30605": Geen ruimte over op
apparaat
STATEMENT: CLUSTER;
Hmm. I wonder why we have XLogFileInit forcing a PANIC for this. At
one time it was called only from critical sections and s
"Sander Steffann" <[EMAIL PROTECTED]> writes:
> 2005-01-15 15:17:46 [30605] PANIC: PANIC: could not write to file
> "/var/lib/pgsql/data/pg_xlog/xlogtemp.30605": Geen ruimte over op apparaat
> STATEMENT: CLUSTER;
Hmm. I wonder why we have XLogFileInit forcing a PANIC for this. At
one time it
Hi,
I was running a CLUSTER on a big database (approx. 8G) and I didn't
anticipate the diskspace usage, so I ran out of diskspace. This is on
PostgreSQL 7.4.6. The backend crashed with the following log messages:
2005-01-15 15:17:46 [30605] PANIC: PANIC: could not write to file
"/var/lib/pgsq
