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 ...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).
lg,k
On Tue, Jul 30, 2013 at 8:23 AM, raghu ram <raghuchennuru@xxxxxxxxx> wrote:
On Tue, Jul 30, 2013 at 4:07 AM, Klaus Ita <klaus@xxxxxxxxxxxxxx> wrote:
Sorry for cross-posting, i read that pg-bug was not the right place for this emailHi 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 83934772013-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 & RegardsRaghu Ram
