Hi,
On Thu, 03 Feb 2005 10:03:34 -0600, Pam Eggler <peggler@hotmail.com> wrote:
> I noticed I was running low on space on my system, so I found this vacuum
> command. I ran it and it failed because it ran out of space:
>
> vacuum mytable;
> FATAL 2: ZeroFill failed to write
> /var/lib/pgsql/data/pg_xlog/xlogtemp.23895: No space left on device
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> The connection to the server was lost. Attempting reset: 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.
I would check your disk space and make sure that you did not run out.
Maybe your var partition is too small. Also you might want to look at
this url: http://www.issociate.de/board/goto/577586/Vacuum_full_-_disk_space_eaten_by_WAL_logfiles.html#msg_577586
> I cleared out that dir and then tried to go back into my database and I get
> this error:
>
> psql fsp
> psql: could not connect to server: No such file or directory
> Is the server running locally and accepting
> connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
>
> Help?
Postgresql is not running anymore. You have to restart it. How you
would do that depends on the operating system you are using. But
usually the startup scripts are in either /etc/rc.d or
/usr/local/etc/rc.d. You could also use the postmaster or pg_ctl to
start it up manually. Read the man pages on what options to pass. I
hope this helps.
Sincerely,
Rick Apichairuk
