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

From
Subject Re: ERROR: could not find tuple for trigger 37463634
Date
Msg-id 30660_1331116069_4F573825_30660_9588_1_9632480C9F82B44294C2302320958E9808415F9A7C@PUEXCB2F.nanterre.francetelecom.fr
Whole thread Raw
In response to ERROR: could not find tuple for trigger 37463634  (<mdione.ext@orange.com>)
List pgsql-general
De : pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] De la part de mdione.ext@orange.com
>   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.

  Ok, the vacuum finished, but I still get the same error. Here's the rest
of the info:

pnssi_profiles_bench=# select * from pg_class where oid=2620 or oid=1255 or oid=1259;
  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              |    258153645 | {=r/postgres} | 
 pg_class   |           11 |      83 |         0 |       10 |     0 |           0 |             0 |      490 |
17440|             0 |             0 | t           | f           | f         | r       |       27 |         0 | t
  | f          | f               | f           | f              | f              |    258153672 | {=r/postgres} | 
 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              |    258153674 | {=r/postgres} | 
(3 rows)

--
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.


pgsql-general by date:

Previous
From: Sergey Konoplev
Date:
Subject: Re: Complex transactions without using plPgSQL Functions. It is possible?
Next
From: Martin Gregorie
Date:
Subject: Re: Complex transactions without using plPgSQL Functions. It is possible?