the table o tables have triggers?
try to use COMMIT
--- On Thu, 6/26/08, Robert James <srobertjames(at)gmail(dot)com> wrote:
From: Robert James <srobertjames(at)gmail(dot)com>
Subject: [GENERAL] Undocumented Postgres error: "failed to fetch old tuple for AFTER trigger"
To: "Postgres General" <pgsql-general(at)postgresql(dot)org>
Date: Thursday, June 26, 2008, 8:28 PM
I'm running a very large series of commands - mainly DDL but some DML as well - in a large transaction. I get the following error, which doesn't seem to be documented:
"ERROR: failed to fetch old tuple for AFTER trigger
There are no triggers that I'm aware of. I've gotten this error when running the transaction on two different instances of the database. I also did a VACUUM FULL, which didn't help.
Breaking down the commands into a series of about 7 smaller transactions works fine. Each transaction runs totally fine by itself. But, when I run them all in one giant transaction, I get errors.
I'm running Postgres 8.2.1 on Windows XP. If anyone can help, I'd be very greatful.
In response to
pgsql-general by date
|Next:||From: Tom Lane||Date: 2008-06-26 21:48:53|
|Subject: Re: Undocumented Postgres error: "failed to fetch old tuple for AFTER trigger" |
|Previous:||From: Ron Mayer||Date: 2008-06-26 21:11:21|
|Subject: Re: Probably been asked a hundred times before.|