Re: [ADMIN] ERROR: XX001 (Critical and Urgent)

Поиск
Список
Период
Сортировка
Искать
От
Kevin Grittner
Тема
Re: [ADMIN] ERROR: XX001 (Critical and Urgent)
Дата
в 11:36:02
Msg-id
4BE3D0EF020000250003137D@gw.wicourts.gov
Ответ на
Список
Дерево обсуждения
ERROR: XX001 (Critical and Urgent) Siddharth Shah <siddharth.shah@elitecore.com>
Re: [ADMIN] ERROR: XX001 (Critical and Urgent) "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Siddharth Shah  wrote:
 
> * fsync is off*
 
If you are running the database with fsync off and there is any sort
of unusual termination, your database will probably be corrupted.  I
recommend restoring from your last good backup.  If you don't have
one, recovery is going to be painful; I recommend contracting with
one of the many companies which off PostgreSQL support.  (I'm not
affiliated with any of them.)
 
> I have tried with making fsync on
 
That may help prevent further corruption, but will do nothing to
help recover from the damage already done.
 
> Postgres Version : 8.4.3 (Migrated data from 8.4.1)
 
What do you mean by that?  You installed 8.4.3 and reindexed hash
indexes?
 
> What can be issue ? Is it issue coming after database table
> corruption
 
Yes.
 
> Can fsync on can prevent such (corruption) scenarios ?
 
Yes.
 
-Kevin
В списке pgsql-novice по дате отправления
От: Siddharth Shah
Дата:
От: Tom Lane
Дата:
Сообщение: Re: Superuser lacking privs
FAQ