From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Klaus Ita <klaus(at)worstofall(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: corrupted files |
Date: | 2013-07-29 21:38:31 |
Message-ID: | CAM-w4HNFuZ85ZFGZ1AS3Peoe2S88rzwkNxwwSdG9zcfFKWrAwg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-general |
On Mon, Jul 29, 2013 at 10:19 PM, Klaus Ita <klaus(at)worstofall(dot)com> wrote:
> My feeling is, that 'something' got confused with hot-standby and
> wal_archiving leading to this situation, that seems to be partially xfs
> caused?????? xfs_repair mentionned some missing files, that pg did not
> expect to have (maybe truncated tables??).
This doesn't sound like a problem with wal archiving or hot standby.
It doesn't sound like a postgres bug at all. It sounds like your
filesystem deleted some files that Postgres needs. The pg clog
contains critical data that you're not going to be able to get by
without.
I suggest posting to pgsql-general and include more information to
help people help you. You say xfs_repair mentioned some missing files
but don't include the actual error messages for example.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Klaus Ita | 2013-07-29 21:49:31 | Re: corrupted files |
Previous Message | Klaus Ita | 2013-07-29 21:19:56 | corrupted files |
From | Date | Subject | |
---|---|---|---|
Next Message | Klaus Ita | 2013-07-29 21:49:31 | Re: corrupted files |
Previous Message | Klaus Ita | 2013-07-29 21:19:56 | corrupted files |