Re: "too many trigger records found for relation xyz"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mikko Partio" <mpartio(at)gmail(dot)com>
Cc: "Zdenek Kotala" <Zdenek(dot)Kotala(at)sun(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: "too many trigger records found for relation xyz"
Date: 2008-04-08 18:30:48
Message-ID: 5484.1207679448@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Mikko Partio" <mpartio(at)gmail(dot)com> writes:
> On Tue, Apr 8, 2008 at 6:38 PM, Zdenek Kotala <Zdenek(dot)Kotala(at)sun(dot)com> wrote:
>> 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?

> I tried it on a fresh instance but it went through with no errors :(

Is it possible that anything was doing a VACUUM FULL on pg_class
concurrently with your schema changes on these tables? The behavior
looks suspiciously like some problems we've seen before wherein rows
ended up with the wrong commit-bit markings...

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Amiel 2008-04-08 18:32:43 More SSL crash woes
Previous Message Craig Ringer 2008-04-08 18:27:08 Re: Determining weather a query fired a trigger