Re: Filesystem crash - corupted database
От
Scott Marlowe
Тема
Re: Filesystem crash - corupted database
Дата
Msg-id
dcc563d10709260745n7f715ecdke8b83918f8f81e05@mail.gmail.com
Ответ на
Filesystem crash - corupted database (Martin Bednář)
Список
Дерево обсуждения
Filesystem crash - corupted database Martin Bednář <bednar@triax.cz>
Re: Filesystem crash - corupted database Martijn van Oosterhout <kleptog@svana.org>
Re: Filesystem crash - corupted database "Scott Marlowe" <scott.marlowe@gmail.com>
On 9/26/07, Martin Bednář wrote: > Hi, > > It's possible to extract data directly from data files ? > I have two tablespaces one for data and one for indexes. > After filesystem crash I lost my /var/lib/postgresql/data folder :( All > data is in /lost+found :(, I found folders with data and index tablespe > that looks ok. > It's possible to directly access these files and extract data as CSV for > example ? > Or it's possible "mount" these tablespaces to new database instance ? You can read them with a hex dump program, but that's about it. The data may well be too corrupted to use anyway. OTOH, if the files are intact and you can rename them back to what they were you might be able to get your db back up. But I wouldn't count on it. > btw: I know - restore from backups, but DB is too big, and I have > backups 6days ago. That's why there's PITR. If you had been backing up with PITR, then you could roll forward your standby machine and be right back up. Use this to make a case to the powers that be that you need better backup procedures and hardware to handle your data. The cost of your data is much higher than the cost of the hardware it lives on.
В списке pgsql-general по дате отправления