Thread: 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
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
Ned Lilly wrote: > Has anyone seen this behavior? It's corrupted a production database. Hi Ned, Just as information filler, which version of PostgreSQL, and which operating system? :-) Regards and best wishes, Justin Clift > ERROR: heap_mark4update: (am)invalid tid > WARNING: Error occurred while executing PL/pgSQL function issuewomaterial > WARNING: line 40 at SQL statement -- "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there." - Indira Gandhi
I don't know if this is terribly helpful, but the message was around in 7.2.x, look at src/backend/access/heap/heapam.c around line 1808 (or 1823 in the 7.3.x code) That said, I've not seen it before, perhaps you can expand upon what your function is doing? Robert Treat On Mon, 2003-01-27 at 11:06, Ned Lilly wrote: > 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 > > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
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