ERROR: could not find tuple for trigger 37463634 - Mailing list pgsql-general

  Short and simple: I'm trying to do the following:

postgres@master-db01:~$ psql pnssi_profiles_bench
psql (9.0.3)
Type "help" for help.

pnssi_profiles_bench=# drop SCHEMA _pnssi_slony_bench_profiles_01_110 cascade;
ERROR:  could not find tuple for trigger 37463634

  As you can see, this is a slony setup, but I'm not sure that's relevant.
Other info:

pnssi_profiles_bench=# select * from pg_depend where objid=37463634;
 classid |  objid   | objsubid | refclassid | refobjid | refobjsubid | deptype
---------+----------+----------+------------+----------+-------------+---------
    2620 | 37463634 |        0 |       1255 | 37462497 |           0 | n
    2620 | 37463634 |        0 |       1259 | 19914767 |           0 | a
(2 rows)

pnssi_profiles_bench=# select * from pg_class where oid=1255;
 relname | relnamespace | reltype | reloftype | relowner | relam | relfilenode | reltablespace | relpages | reltuples |
reltoastrelid| reltoastidxid | relhasindex | relisshared | relistemp | relkind | relnatts | relchecks | relhasoids |
relhaspkey| relhasexclusion | relhasrules | relhastriggers | relhassubclass | relfrozenxid |    relacl     | reloptions 

---------+--------------+---------+-----------+----------+-------+-------------+---------------+----------+-----------+---------------+---------------+-------------+-------------+-----------+---------+----------+-----------+------------+------------+-----------------+-------------+----------------+----------------+--------------+---------------+------------
 pg_proc |           11 |      81 |         0 |       10 |     0 |           0 |             0 |      304 |      3635 |
        2836 |             0 | t           | f           | f         | r       |       25 |         0 | t          | f
       | f               | f           | f              | f              |    150006110 | {=r/postgres} | 
(1 row)


pnssi_profiles_bench=# select * from pg_class where oid=2620;
  relname   | relnamespace | reltype | reloftype | relowner | relam | relfilenode | reltablespace | relpages |
reltuples| reltoastrelid | reltoastidxid | relhasindex | relisshared | relistemp | relkind | relnatts | relchecks |
relhasoids| relhaspkey | relhasexclusion | relhasrules | relhastriggers | relhassubclass | relfrozenxid |    relacl
|reloptions  

------------+--------------+---------+-----------+----------+-------+-------------+---------------+----------+-----------+---------------+---------------+-------------+-------------+-----------+---------+----------+-----------+------------+------------+-----------------+-------------+----------------+----------------+--------------+---------------+----------

 pg_trigger |           11 |   10732 |         0 |       10 |     0 |       11738 |             0 |      312 |
11814|          2336 |             0 | t           | f          | f         | r       |       15 |         0 | t
 | f          | f               | f           | f              | f              |    150006329 | {=r/postgres} |  
(1 row)

  I don't have the rest of the info (the entry in pg_class with OID 1259)
because right now I'm running a preventive VACUUM, which it's taking ages.

  What I understand is that it seems that somehow I got some references to objects
that do not exist anymore, so I think I should run the equivalent of fsck I this
database. My speculations apart, how to proceed to unlock this situation?

--
Marcos Dione
SysAdmin
Astek Sud-Est
pour FT/TGPF/OPF/PORTAIL/DOP/HEBEX @ Marco Polo
04 97 12 62 45 - mdione.ext@orange.com




_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorization.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange shall not be liable if this message was modified, changed or
falsified.
Thank you.