Re: no space left on device

>
>Note that the pg_xlog dir is huge! Here's its contents:
>
>[postgres - DB/pg_xlog]$ ls -al
>total 32816
>drwx------ 2 postgres admin 4096 Mar 29 2003 .
>drwx------ 6 postgres admin 4096 Jan 9 15:04 ..
>-rwx------ 1 postgres admin 16777216 Jan 9 15:09 0000000000000001
>-rwx------ 1 postgres admin 16777216 Mar 29 2003 0000000000000002
>
>What are these files, and what can I do to resolve this issue?
>
>
The are check_point files. You need them. Have you ran a vacuum recently?

Sincerely,

Joshua D. Drake

>Thx,
>
>Zeb
>
>
>--
>DEBUG: statistics collector process (pid 2523) exited with exit code 1
>PGSTAT: Error closing temp stats file
>PGSTAT: /usr/local/G101/App/DB/./global/pgstat.tmp.7823: No space left on
>device
>PGSTAT: AbDEBUG: statistics collector process (pid 2979) exited with exit
>code
>1
>FATAL 2: write of clog file 43, offset 188416 failed: No space left on
>device
>DEBUG: server process (pid 3741) exited with exit code 2
>DEBUG: terminating any other active server processes
>NOTICE: Message from PostgreSQL backend:
> The Postmaster has informed me that some other backend
> died abnormally and possibly corrupted shared memory.
> I have rolled back the current transaction and am
> going to terminate your database system connection and exit.
> Please reconnect to the database system and repeat your query.
>NOTICE: Message from PostgreSQL backend:
> The Postmaster has informed me that some other backend
> died abnormally and possibly corrupted shared memory.
> I have rolled back the current transaction and am
> going to terminate your database system connection and exit.
> Please reconnect to the database system and repeat your query.
>NOTICE: Message from PostgreSQL backend:
> The Postmaster has informed me that some other backend
> died abnormally and possibly corrupted shared memory.
> I have rolled back the current transaction and am
> going to terminate your database system connection and exit.
> Please reconnect to the database system and repeat your query.
>DEBUG: all server processes terminated; reinitializing shared memory and
>semaph
>ores
>DEBUG: database system was interrupted at 2004-01-09 05:22:52 EST
>DEBUG: checkpoint record is at 0/138CFD4
>DEBUG: redo record is at 0/138CFD4; undo record is at 0/0; shutdown FALSE
>DEBUG: next transaction id: 45811837; next oid: 65205
>DEBUG: database system was not properly shut down; automatic recovery in
>progre
>ss
>DEBUG: redo starts at 0/138D014
>FATAL 2: write of clog file 43, offset 188416 failed: No space left on
>device
>DEBUG: startup process (pid 3785) exited with exit code 2
>DEBUG: aborting startup due to startup process failure
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL