Since you can recreate or restore the data, erase everything in your $PGDATA
directory and reinitialize the database. While you are at it, you should
consider putting $PGDATA on a filesystem with more space.
--
Randy Hall - Red Hat Certified Engineer - Ex-Great Bridge PostgreSQL Expert
Resume: http://members.home.net/rthall3
----- Original Message -----
From: "Nick Fankhauser" <nickf@ontko.com>
To: "pgsql-admin" <pgsql-admin@postgresql.org>
Sent: Tuesday, September 11, 2001 7:16 AM
Subject: [ADMIN] Can't get postmaster to restart after removing WAL files
> Hi all-
>
> I caused a crash by filling up the filesystem that pg_xlog lives on whilst
> doing a vacuum analyze. When I looked at the remains, there were 3 WAL
files
> out there & no space left.
>
> I tried simply restarting (/etc/init.d/postgresql start) in the hopes that
> the mess would get cleaned, but with no luck. The startup script reported
> success, but no postmaster was running.
>
> I tried removing the WAL files & restarting again with the same results-
the
> startup script reports success, but postmaster isn't running.
>
> I'm not worried about the data- this is on a demo system, so I can
> regenerate it quickly, but I can't even get the postmaster started so I
can
> begin the restore. I guess I've learned that removing a WAL file is a Bad
> Idea (tm)... but now I need a good idea to get me back to the starting
> point.
>
> Any ideas?
>
> TIA-
>
> -Nick
>
>
> ---------------------------------------------------------------------
> Nick Fankhauser
>
> nickf@doxpop.com Phone 1.765.965.7363 Fax 1.765.962.9788
> doxpop - Court records at your fingertips - http://www.doxpop.com/
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://www.postgresql.org/search.mpl
>