| From: | Shane <shane-pgsql(at)cm(dot)nu> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Database corruption |
| Date: | 2007-05-19 05:46:56 |
| Message-ID: | 20070519054655.GA5781@cm.nu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, May 18, 2007 at 09:11:58PM -0400, Alvaro Herrera wrote:
> >
> > It's clear something's amiss with the database but I'm not
> > sure where to go from here. Is any data from bayes_token
> > recoverable, should I just delete the data in that table or
> > does the whole database need to be dropped and recreated?
>
> Hang on. You may still recover the data. What range of files do you
> see in the pg_clog directory? Also, what version is this?
continuum:~# ls /var/lib/postgresql/8.1/main/pg_clog/
0020 0025 002A 002F 0034 0039 003E 0043 0048 004D 0052 0057
0021 0026 002B 0030 0035 003A 003F 0044 0049 004E 0053 0058
0022 0027 002C 0031 0036 003B 0040 0045 004A 004F 0054 0059
0023 0028 002D 0032 0037 003C 0041 0046 004B 0050 0055 005A
0024 0029 002E 0033 0038 003D 0042 0047 004C 0051 0056 005B
This is postgresql 8.1.8 from Debian. I've seen no sign of
disk corruption thus far. It's a raid5 so would see a
failure though not a real corruption if that actually
happened.
Shane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joris Dobbelsteen | 2007-05-19 08:14:33 | Re: Fault Tolerant Postgresql (two machines, two postmasters, one disk array) |
| Previous Message | Alvaro Herrera | 2007-05-19 03:51:51 | Re: Large Database Restore |