| From: | Raghu Ram <raghuchennuru(at)gmail(dot)com> |
|---|---|
| To: | Gabriel Sánchez Martínez <gabrielesanchez(at)gmail(dot)com> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: invalid OID warning after disk failure |
| Date: | 2014-11-17 08:28:12 |
| Message-ID: | CALnrrJSmyZgKhaP-Stag2txWr2wA6ErU8tOh340NB+pH44yqOA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Nov 17, 2014 at 10:20 AM, Gabriel Sánchez Martínez <
gabrielesanchez(at)gmail(dot)com> wrote:
>
> The situation appears to be stable now, but upon running REINDEX and
> VACUUM on one of the databases, I get the following:
>
> WARNING: relation "pg_attrdef" TID 1/1: OID is invalid
> WARNING: relation "pg_attrdef" TID 1/2: OID is invalid
> WARNING: relation "pg_attrdef" TID 1/3: OID is invalid
> ...
>
> Should I drop the database and restore it from a backup? My most recent
> backup is from late September, so I would lose some data. I also backed up
> what I could as soon as the disks started giving errors, but I don't know
> if I can trust that.
>
> Should I drop the entire cluster?
>
>
>
are you receiving any kind of error messages,while taking database dump
with "pg_dump" utility.
If you are not receiving any kind of error message,try to take a database
dump and restore database dump file in another database server and perform
all sanity checks. If all sanity checks are working fine,you can create a
new cluster and restore all database dump's.
Thanks & Regards
Raghu Ram
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pawel Veselov | 2014-11-17 08:52:03 | incremental digest (and other) functions? |
| Previous Message | Gabriel Sánchez Martínez | 2014-11-17 04:50:28 | invalid OID warning after disk failure |