Re: Fwd: corrupted files

Поиск
Список
Период
Сортировка
От Klaus Ita
Тема Re: Fwd: corrupted files
Дата
Msg-id CAGrfkYMQdTKVgr=Z30UOWvSYZS7WDN6Bf56V3L5rFAOPqqWwqg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Fwd: corrupted files  (raghu ram <raghuchennuru@gmail.com>)
Ответы Re: Fwd: corrupted files  (bricklen <bricklen@gmail.com>)
Список pgsql-general
Дерево обсуждения
Hi!

Thank you, I actually tried that and it seems that only lead to even more corrupted data. I am currently trying to recover the 'hot-standby' host that is also unhappy about one of the wal_files. I am looking at the wal with less and see only data i do not care about in it (mostly session-logging/statistics data).

I am trying to remember, there was a tool that plotted the contents of the wal_files in a more readable format ...

lg,k


On Tue, Jul 30, 2013 at 8:23 AM, raghu ram <raghuchennuru@gmail.com> wrote:

On Tue, Jul 30, 2013 at 4:07 AM, Klaus Ita <klaus@worstofall.com> wrote:
Sorry for cross-posting, i read that pg-bug was not the right place for this email

Hi list!

depressed me gets error messages like these:

2013-07-29 20:57:09 UTC <xaxos_mailer%xaxos_de> ERROR:  could not access status of transaction 8393477
2013-07-29 20:57:09 UTC <xaxos_mailer%xaxos_de> DETAIL:  Could not open file "pg_clog/0008": No such file or directory.

combined with the error output of queries that  do not work.

I looked in pg_clog and correct, 0008 is missing.



You can recreate a missed "pg_clog" file with below command:

dd if=/dev/zero of=~/9.1/main/pg_clog/0008  bs=256k count=1 (To make the uncommitted record as they haven't been committed.)

and then try to start the cluster.

Thanks & Regards
Raghu Ram


В списке pgsql-general по дате отправления:

Предыдущее
От: Klaus Ita
Дата:
Сообщение: Recovery failure
Следующее
От: Loïc Rollus
Дата:
Сообщение: Re: Trigger and deadlock