| From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
|---|---|
| To: | Mikko Partio <mpartio(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: "too many trigger records found for relation xyz" |
| Date: | 2008-04-08 15:38:37 |
| Message-ID: | 47FB917D.5040106@sun.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Mikko Partio napsal(a):
> On Tue, Apr 8, 2008 at 5:26 PM, Mikko Partio <mpartio(at)gmail(dot)com> wrote:
>
>> Ok I removed the faulty tuple and nothing catastrophical happened. I can
>> do a pg_dump now, but I still can't remove the one remaining table:
>>
>> # drop table xyz ;
>> ERROR: too many trigger records found for relation "xyz"
>>
>> Any insight for this problem?
>>
>>
>
> I managed to solve the situation with the help of this thread:
> http://archives.postgresql.org/pgsql-bugs/2007-02/msg00167.php
>
> Everything seems to be ok for now, but I'm still curious what caused to
> whole mess to begin with.
It is really strange. It would be nice to have reproduce scenario. Can you run
same DDL command which invoke a catalog corruption on test database cluster?
Zdenek
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2008-04-08 15:40:27 | Re: Problem after VACUUM ANALYZE |
| Previous Message | Richard Huxton | 2008-04-08 15:18:12 | Re: Determining weather a query fired a trigger |