From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
---|---|
To: | tony <tony(at)animaproductions(dot)com>, Petre Daniel <dani(at)cyber(dot)ro> |
Cc: | postgres list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: database problem.. |
Date: | 2002-03-05 17:35:39 |
Message-ID: | 200203051735.g25HZeLx001856@www1.translationforge |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Le Mardi 5 Mars 2002 17:13, tony a écrit :
> If your postgresql version is older than 7.1 then say adieu to your data
> now...
I experienced a crash on a Linux station (power-failure) and noticed that
some row-level locking prevented PostgreSQL from starting up.
After backup, you may need to start the single-user version of postgreSQL.
This will unlock rows :
1) Copy /var/lib/pgsql/data/ to another computer. The other computer should
run the exact same version of PostgreSQL. Otherwize, wait for a more detailed
help from this forum.
2) postgresql DATABASE_NAME will start PostgreSQL in single-user mode.
Can anyone confirm, I am not familiar with database recovery.
/Jean-Michel POURE
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-03-05 17:37:18 | Re: storing intermediate results in recursive plpgsql functions |
Previous Message | Jeff Boes | 2002-03-05 17:32:08 | Re: Migration problem - serial fields |