We've done a bit more digging, and think we understand the problem. Looks like 7.3.1 is just now taking advantage of a
performanceflag that has been ignored up to now. The error message is a bit unclear.
When we close this out internally, we'll document our findings to the list. So, in short, "never mind."
Thanks,
NL
----- Original Message -----
From: "Ned Lilly" <ned@nedscape.com>
To: "PostgreSQL Hackers" <pgsql-hackers@postgresql.org>
Sent: Monday, January 27, 2003 11:06 AM
Subject: Re: [HACKERS] urgent: db corruption - invalid TIDs?
ps - this is on 7.3.1. It never happened on 7.2.3...
----- Original Message -----
From: "Ned Lilly" <ned@nedscape.com>
To: "PostgreSQL Hackers" <pgsql-hackers@postgresql.org>
Sent: Monday, January 27, 2003 11:04 AM
Subject: [HACKERS] urgent: db corruption - invalid TIDs?
Has anyone seen this behavior? It's corrupted a production database.
ERROR: heap_mark4update: (am)invalid tid
WARNING: Error occurred while executing PL/pgSQL function issuewomaterial
WARNING: line 40 at SQL statement