Re: Help. Pg not running
От | Asidha Luhwidyanto |
---|---|
Тема | Re: Help. Pg not running |
Дата | |
Msg-id | 3196.61.94.149.13.1057024781.squirrel@webmail.dijogja.com обсуждение исходный текст |
Ответ на | Re: Help. Pg not running (Sam Barnett-Cormack <s.barnett-cormack@lancaster.ac.uk>) |
Ответы |
Re: Help. Pg not running
(Sam Barnett-Cormack <s.barnett-cormack@lancaster.ac.uk>)
|
Список | pgsql-admin |
Thank's I have trying to restarting pg and copying xlogs file from the last backup. Until some trial and error, it working. DEBUG: database system was interrupted at 2003-06-28 02:41:38 JAVT DEBUG: CheckPoint record at (0, 12369592) DEBUG: Redo record at (0, 12369592); Undo record at (0, 0); Shutdown FALSE DEBUG: NextTransactionId: 14017; NextOid: 32252 DEBUG: database system was not properly shut down; automatic recovery in progress... DEBUG: ReadRecord: record with zero len at (0, 12369656) DEBUG: redo is not required DEBUG: database system is in production state And now i can backup all db. I will upgrade my last 7.12 version to 7.3. Maybe i need to use extended 3 for my linux filesystem and installing UPS for protecting my PG server. Thank's Sam Barnet & Scott Marlowe for your guid. Asidha Luhwidyanto -------------------- http://dijogja.com/ for information of Jogja-Java-Indonesia > On Mon, 30 Jun 2003, Asidha Luhwidyanto wrote: > >> Dear All, >> >> I'm sorry, I'm a beginer in PostgreSQL. >> >> I have problem with my PostgreSQL after my server un complete >> shutdown. When i want to run postmaster there some error massage and >> postmaster can't run. >> >> this is the massage : >> > <SNIP ERRORS> >> >> What i must to do to fixing this problem ? > > This is exactly what happened to me before - the WAL (write-ahead-logs) > or xlogs have become corrupt, or more like;ythe pg_control file got > wiped. What you need to do is: > > 1) backup your xlogs and pg_control, just in case. > > 2) touch to make an empty pg_control > > 3) read the manpage on pg_resetxlog - figure out the correct > transaction id and other values, and run the program. Possibly backup > the entire DB directory structure, just in case. > > 4) Trial and error (possibly) until you get the server to start again. > Then do *nothing* until you have dumped the db to a file, and cleanly > resotred from it. You should also manually check for inconsistencies, > although if you have correctly used contraints it should barf on input > if there are any. Assuming your DB is fully normalised. > > Hope that helps > > -- > > Sam Barnett-Cormack > Software Developer | Student of Physics & > Maths UK Mirror Service (http://www.mirror.ac.uk) | Lancaster > University > > ---------------------------(end of > broadcast)--------------------------- TIP 1: subscribe and unsubscribe > commands go to majordomo@postgresql.org
В списке pgsql-admin по дате отправления: