Обсуждение: DROP TRIGGER

hi all again

i have little complex database was used in tests of a program
in ordinal way (no manual expirements with pg_catalog have done)

now the database seems damaged in strange manner:

Postgres cannot drop nor create some triggers
(he was thinking about an hour on the query then i have cancelled)

The undroppable and uncreateable triggers are all on the one table of the DB
ANY OTHER triggers looks fine (drop and create)

VACUUM FULL VERBOSE ANALYZE;
drove the Postgres to nirvana too with output:

bla-bla-bla some table pf pg_catalog
....
INFO:  --Relation pg_catalog.pg_type--
INFO:  Pages 7: Changed 0, reaped 1, Empty 0, New 0; Tup 375: Vac 0, Keep/VTL
0/0, UnUsed 10, MinLen 144, MaxLen 144; Re-using: Free/Avail. Space
1664/1472; EndEmpty/Avail. Pages 0/1.       CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO:  Index pg_type_oid_index: Pages 2; Tuples 375: Deleted 0.       CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO:  Index pg_type_typname_nsp_index: Pages 8; Tuples 375: Deleted 0.       CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO:  Rel pg_type: Pages: 7 --> 7; Tuple(s) moved: 0.       CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO:  Analyzing pg_catalog.pg_type

that's all.


I will not drop this DB and waiting for your reply.

Dear developers if you suspect a bug, i would gladly provide any info on your
request even dump.

sad <sad@bankir.ru> writes:
> ... now the database seems damaged in strange manner:
> Postgres cannot drop nor create some triggers 
> (he was thinking about an hour on the query then i have cancelled)

Could you try it again and get a stack trace to show exactly where it's
hung up?
        regards, tom lane