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

Поиск
Список
Период
Сортировка
От Mikko Partio
Тема Re: "too many trigger records found for relation xyz"
Дата
Msg-id 2ca799770804081049l3854620fpcf31f4dfe239baa4@mail.gmail.com
обсуждение исходный текст
Ответ на Re: "too many trigger records found for relation xyz"  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Ответы Re: "too many trigger records found for relation xyz"  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general


On Tue, Apr 8, 2008 at 6:38 PM, Zdenek Kotala <Zdenek.Kotala@sun.com> wrote:
Mikko Partio napsal(a):

On Tue, Apr 8, 2008 at 5:26 PM, Mikko Partio <mpartio@gmail.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

В списке pgsql-general по дате отправления:

Предыдущее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: Persistent objects within PG or the availability of non-logged tables or databases?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: tsvector_update_trigger throws error "column is not of tsvector type"