Re: ERROR: cache lookup failed for relation 438095645
От | Joe Markwardt |
---|---|
Тема | Re: ERROR: cache lookup failed for relation 438095645 |
Дата | |
Msg-id | 1120749258.27667.63.camel@Odin обсуждение исходный текст |
Ответ на | Re: ERROR: cache lookup failed for relation 438095645 (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: ERROR: cache lookup failed for relation 438095645
|
Список | pgsql-general |
On Wed, 2005-07-06 at 23:36 -0400, Tom Lane wrote: > Joe Markwardt <joe@avsupport.com> writes: > > On Wed, 2005-07-06 at 14:04 -0400, Tom Lane wrote: > >> They appear to be triggers for a foreign-key constraint between > >> pl_inventory_analyzer_files_table and pl02_status_table ... so I guess > >> the question is what happened to the latter? > > > I'm not sure. As far as I can tell nothing has happened to the > > pl02_status_table, nor should anything have happened to it recently. > > Well, that's just plain bizarre... > > The next thing to check is whether the OID mentioned in pg_trigger > (which I forgot already) is the same as the OID shown in pg_class, ie > select oid from pg_class where relname = 'pl02_status_table'. oid ----------- 438094756 (1 row) The oid that shows up in the error is 438095645. the oid for the pl02_status_table does not show up in any of the rows in pg_trigger that have the oid from the error in them. The oid for the status table does show up in a few other rows in pg_trigger (attached file), which makes sense since its referenced in at least 2 other tables with foreign keys, and it still is being replicated by slony so it has that trigger on it as well. Thanks Joe
Вложения
В списке pgsql-general по дате отправления: