Postgres Pro
Downloads
Home   >   mailing lists

Thread: startup failed! fatal error

startup failed! fatal error

From
"Jeff Lu"
Date:
using 7.1.2

UGENT

Database startup failed

DEBUG:  redo done at (1, 3923880100)
FATAL 2:  XLogFlush: request is not satisfied
postmaster: Startup proc 1016 exited with status 512 - abort

What can I do to recover?

Thanks

Re: startup failed! fatal error

From
"Hero"
Date:
> using 7.1.2
>
> UGENT
>
> Database startup failed
>
> DEBUG:  redo done at (1, 3923880100)
> FATAL 2:  XLogFlush: request is not satisfied
> postmaster: Startup proc 1016 exited with status 512 - abort
>
> What can I do to recover?
>
> Thanks

your database store file is bad,
you must be use initdb create new template,but remember your database will
be destory.

Re: startup failed! fatal error

From
"Henshall, Stuart - WCP"
Date:
There is a contrib utility (pg_resetxlog) that allows clearing of pg_xlog.
It may be worth trying this. Note though clearing the WAL files can leave
the database in an inconsistent state. If you can I'd make a back up of the
entire data area then ask on general or maybe bugs. I suspect some people
would be interested in working out exactly what is stopping it starting.
- Stuart

-----Original Message-----
From: Hero [mailto:herolin@yam.com]
Sent: 05 January 2002 07:19
To: Jeff Lu; pgsql-cygwin@postgresql.org
Subject: Re: [CYGWIN] startup failed! fatal error



> using 7.1.2
>
> UGENT
>
> Database startup failed
>
> DEBUG:  redo done at (1, 3923880100)
> FATAL 2:  XLogFlush: request is not satisfied
> postmaster: Startup proc 1016 exited with status 512 - abort
>
> What can I do to recover?
>
> Thanks

your database store file is bad,
you must be use initdb create new template,but remember your database will
be destory.


---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org