-------- Messaggio Originale --------
Oggetto: Re: Crash with data corruption under Windows
Da: Scott Marlowe <scott.marlowe@xxxxxxxxx>
On Mon, Feb 23, 2009 at 9:49 AM, Nicola Mauri <nicola.mauri@xxxxxxx> wrote:
-------- Messaggio Originale --------
Oggetto: Re: Crash with data corruption under Windows
Da: Scott Marlowe <scott.marlowe@xxxxxxxxx>
Usually when I see the permission denied thing there's anti-virus
software hard locking pgsql files in the middle of the day.
Have you experienced data loss too in that case?
(however, we already excluded pgsql directories from anti-virus scanning).
I've not, but I rarely run postgresql under windows. When we do it's
on a laptop for personal use / demo use. All our servers run Linux.
However, on this list, when I've seen this happen, it has been known
to result in data loss.
Note that once your database is corrupted, no amount of fixing can
make it safe to keep using. you need to get a good reliable dump from
it, reinitdb and reload your data. So not trust a database that's
gotten corrupted and seems mostly fixed. It's a timebomb.
Hi Scott,
we had to recreate the cluster and reload data from a dump, because we
were unable to read any table (some critical indexes was broken).
However we would like to try to recovery the most recent data from the
corrupted datafiles (as a help for manual insertion). Is there any
method to extract raw data from the pgsql table files?
regards,
Nicola
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
