From: | "Mikko Partio" <mpartio(at)gmail(dot)com> |
---|---|
To: | "Zdenek Kotala" <Zdenek(dot)Kotala(at)sun(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 17:49:47 |
Message-ID: | 2ca799770804081049l3854620fpcf31f4dfe239baa4@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Apr 8, 2008 at 6:38 PM, Zdenek Kotala <Zdenek(dot)Kotala(at)sun(dot)com> wrote:
> 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?
I tried it on a fresh instance but it went through with no errors :(
Regards
Mikko
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-04-08 17:57:21 | Re: tsvector_update_trigger throws error "column is not of tsvector type" |
Previous Message | Joshua D. Drake | 2008-04-08 17:27:11 | Re: Persistent objects within PG or the availability of non-logged tables or databases? |