[snip] I believe this is fixed as of 8.2 --- can you duplicate it
there? (No, backpatching the fix is not practical.)
No, I was not able to duplicate it on 8.2, so I think it's fixed (given
that on 8.1 the errors are triggered almost 100% of the runs).
How sure are you about that
everything ok.
- Original Message -
From: Csaba Nagy [EMAIL PROTECTED]
To: Postgres general mailing list pgsql-general@postgresql.org
Sent: Friday, January 26, 2007 10:06 AM
Subject: Re: [GENERAL] too many trigger records found for relation item -
[snip] I believe this is fixed
Csaba Nagy [EMAIL PROTECTED] writes:
And BTW, I have seen something similar while creating temporary tables
which should not conflict even with the same table name I think...
I've heard reports of that, but never been able to duplicate it ...
regards, tom lane
On Fri, Jan 26, 2007 at 02:33:05PM +0100, Furesz Peter wrote:
I have the same problem yesterday. I got this error when I try to disable
the trigger in pg_catalog:
UPDATE pg_catalog.pg_class SET reltriggers = 0 WHERE oid =
'foobar'::pg_catalog.regclass';
Well duh. The error is precisely
[Update: the post didn't make it to the list probably due to the attachment, so
I resend it inlined... and I was not able to trigger the same behavior on 8.2,
so it might have been already fixed.]
[snip]
Well, if you can show a reproducible test case, I'd like to look at it.
OK, I have a test
Csaba Nagy [EMAIL PROTECTED] writes:
Well, if you can show a reproducible test case, I'd like to look at it.
OK, I have a test case which has ~ 90% success rate in triggering the
issue on my box. It is written in Java, hope you can run it, in any case
you'll get the idea how to reproduce the
On Mon, 2007-01-22 at 20:56, Lenorovitz, Joel wrote:
[snip]
ERROR: too many trigger records found for relation item
I've got this error on a development data base where we were
continuously creating new child tables referencing the same parent
table. The responsible code is in
trigger records found for relation
item -
On Mon, 2007-01-22 at 20:56, Lenorovitz, Joel wrote:
[snip]
ERROR: too many trigger records found for relation item
I've got this error on a development data base where we were
continuously creating new child tables referencing the same parent
table
On Tue, 2007-01-23 at 14:49, Brandon Aiken wrote:
Nevertheless, the database should be able to handle any combination of
syntactically correct SQL statements without throwing errors and
maintaining the database in a consistent state. If what you're saying
is right, the error thrown here is
Csaba Nagy [EMAIL PROTECTED] writes:
The responsible code is in src/backend/commands/trigger.c, and I
think it only happens if you manage to create/drop a new trigger (which
also could be a FK trigger created by a new foreign key referencing that
table, as in our case) exactly between that
On Tue, 2007-01-23 at 15:43, Tom Lane wrote:
Csaba Nagy [EMAIL PROTECTED] writes:
The responsible code is in src/backend/commands/trigger.c, and I
think it only happens if you manage to create/drop a new trigger (which
also could be a FK trigger created by a new foreign key referencing that
Csaba Nagy [EMAIL PROTECTED] writes:
On Tue, 2007-01-23 at 15:43, Tom Lane wrote:
All such code takes exclusive lock on the table, so the above
explanation is impossible.
Well, in that case it must be some other bug as it is readily
reproducible here. My nightly integration has this error
Greetings,
I've had a strange error crop up recently on a table 'Item' which
contains about 60 rows and lives in a development database I'm currently
working on. Since the DB was last freshly created from a dump file
several days ago I've added/dropped/altered a few tables (not
necessarily
Lenorovitz, Joel [EMAIL PROTECTED] writes:
postgres=# select * from item;
ERROR: too many trigger records found for relation item
You could reset the pg_class.reltriggers entry for item to be however
many pg_trigger entries there actually are for the table. I'm curious
how you got into this
14 matches
Mail list logo
