From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | Ned Lilly <ned(at)nedscape(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: urgent: db corruption - invalid TIDs? |
Date: | 2003-01-27 16:32:33 |
Message-ID: | 1043685153.15854.12.camel@camel |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(at)nedscape(dot)com>
> To: "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)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(at)postgresql(dot)org)
From | Date | Subject | |
---|---|---|---|
Next Message | Ned Lilly | 2003-01-27 16:37:16 | Re: urgent: db corruption - invalid TIDs? |
Previous Message | Justin Clift | 2003-01-27 16:07:52 | Re: urgent: db corruption - invalid TIDs? |