From: | eshishki <itparanoia(at)gmail(dot)com> |
---|---|
To: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Corrupted index, what do i do?ruc |
Date: | 2012-01-13 07:41:44 |
Message-ID: | CAO9_yBgcH7za3FQCo5BiA0dgsbX+hGrZ3R=Emgx6g5ETyVMJbA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Since you were running with fsync off, you must have had good backups or
> replication configured, because the documentation warns you that running
> with fsync=off will probably destroy your data and is only for expert users.
Yes, i know, i have a replica and slow disk.
> In case you don't have a current replica or backup: first, before you do
> ANYTHING ELSE follow the instructions here:
>
> http://wiki.postgresql.org/wiki/Corruption
>
> Now - **AFTER** following the instructions above - start the database in
> single user recovery mode. See:
>
> http://www.postgresql.org/docs/current/static/app-postgres.html
>
> where the "--single" command line argument for the "postgres" executable is
> documented.
>
> Once you have a single user mode backend running you can REINDEX then shut
> the backend down, start back up in multi-user mode, and see if you have any
> luck.
Good, may be said wiki page about corruption can be expanded to
include this steps?
--
Evgeny
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Angelico | 2012-01-13 08:03:56 | Re: Operator based on data type |
Previous Message | Craig Ringer | 2012-01-13 06:44:24 | Re: Compiling C function with VC++ for Windows version |