> 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 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
