Re: ERROR: could not find tuple for attrdef NNNNNNNN
| От | Tom Lane | 
|---|---|
| Тема | Re: ERROR: could not find tuple for attrdef NNNNNNNN | 
| Дата | |
| Msg-id | 14519.1224473829@sss.pgh.pa.us обсуждение исходный текст  | 
		
| Ответ на | ERROR: could not find tuple for attrdef NNNNNNNN ("Ridvan Lakas ng Bayan S. Baluyos" <ridvan@baluyos.net>) | 
| Список | pgsql-novice | 
"Ridvan Lakas ng Bayan S. Baluyos" <ridvan@baluyos.net> writes:
> I'm trying to drop a table but I'm receiving the following error,
> pos=# drop table txnmanhours cascade;
> ERROR:  could not find tuple for attrdef 10734091
Hm, what do you get from
    select * from pg_attrdef where oid = 10734091;
If there is a hit, what table does adrelid correspond to?
> Here's my current version,
>  PostgreSQL 8.1.8 on x86_64-pc-linux-gnu, compiled by GCC gcc-4.0.gcc-opt
> (GCC) 4.0.3 (Ubuntu 4.0.3-1ubuntu5)
Not too long ago we fixed an issue wherein a cascaded delete could try
to delete objects more than once, which could give rise to an error
message of this ilk.  I didn't think that 8.1 was vulnerable though.
You might have found some new bug in that logic.  Does txnmanhours
participate in any interesting mutual-reference situations?
            regards, tom lane
		
	В списке pgsql-novice по дате отправления: