Hi Tom,
The version is Postgres 7.1.3.
The problem is no longer there at the moment. I had to get our application
up and running... I ran a vacuum and found one particlar transaction table
in trouble... Sorry I did not keep the error messages. I ended up
truncating the table and vacuuming it again. Then rebuilt the table data.
It seems fine now. It happened again yesterday on our development box. The
table in trouble was PG_ATTRIBUTES this time, as I do not have time to try
and rebuild this table in a development environment, I ended up dropping
and re-creating the DB and loading a production backup.
Thanks
Andrew
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Andrew Bartley" <abartley@evolvosystems.com>
Cc: <pgsql-general@postgresql.org>
Sent: Tuesday, March 05, 2002 4:49 PM
Subject: Re: [GENERAL] FATAL 2: RelationPutHeapTuple: failed to add tuple
> "Andrew Bartley" <abartley@evolvosystems.com> writes:
> > We have been running this particular function for months. Today it just
do=
> > es't want to play the game.
>
> > 2002-03-05 14:09:02 [1014] DEBUG: query: create temp table
request_trans=
> > numbers ( transnumber int8 )
> > 2002-03-05 14:09:02 [1014] FATAL 2: RelationPutHeapTuple: failed to
add =
> > tuple
>
> Yipes, that's not supposed to happen. What PG version is this? If it's
> recent (7.1 or 7.2) I would be interested in poking into the problem
> with a debugger.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
>