| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rodrigo Gonzalez <rjgonzale(at)gmail(dot)com> |
| Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: ERROR: could not open relation with OID 2836 |
| Date: | 2008-06-27 02:23:07 |
| Message-ID: | 6086.1214533387@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Rodrigo Gonzalez <rjgonzale(at)gmail(dot)com> writes:
> Tom Lane wrote:
>> No, it's clear that things are already broken before pg_dump started.
>> You need to show us how to get to this state from a fresh database.
> Interesting....a new problem maybe, or maybe the same one....
> ...
> ERROR: relation "pg_toast_1255" does not exist
Looks like almost the same problem: pg_proc's TOAST table is missing.
But this behavior implies that the pg_class row for it is missing,
whereas the other error suggested that the system catalog entries were
fine but the on-disk file was missing. Odd.
When you say "restored from backup", are you talking about a pg_dump
backup, or what?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ganbold | 2008-06-27 03:04:45 | ERROR: concurrent insert in progress |
| Previous Message | Klint Gore | 2008-06-26 23:44:38 | Re: dblink to non postgresql dbms |