problem delete record error:heap_mark4update

"=?iso-8859-1?Q?frank=5Flupo?=" <frank_lupo@email.it> writes:

I work using postgresql in cygwin version:
PostgreSQL 7.3.2 on i686-pc-cygwin, compiled by GCC gcc (GCC) 3.2 20020927 (prerelease)
When delete a record I recive the message :
heap_mark4update: (am)invalid tid

Do you have a trigger on the table? If so this is probably a known bug.
Update to 7.3.3 and see if it goes away.

regards, tom lane

"=?iso-8859-1?Q?frank=5Flupo?=" writes:

I work using postgresql in cygwin version:
PostgreSQL 7.3.2 on i686-pc-cygwin, compiled by GCC gcc (GCC) 3.2 20020927 (prerelease)
When delete a record I recive the message :
heap_mark4update: (am)invalid tid

Do you have a trigger on the table? If so this is probably a known bug.
Update to 7.3.3 and see if it goes away.

regards, tom lane

Yes, i have the trigger in table. I update on version 7.3.3
The version 7.3.3 is stable?

Thanks

Bye !!
Frank Lupo (Wolf) !!

/\_ _/\
\ o o /
--ooo-----ooo---

--
GPG Key: http://users.jc-hosting.co.uk/frank_lupo/files/publickey.txt

WebSite: http://users.jc-hosting.co.uk/frank_lupo

--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f

Sponsor:
Vuoi acquistare con sconti esclusivi? Con EmailConto Risparmio puoi scontare fino al 20% i tuoi acquisti!
Prova subito la convenienza cliccando qui.
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=837&amp;d=29-5

HeLLo frank...

I have seen that problem, please cecked your table....maybe in your table
any trigger...

regards...

Alam Surya

I work using postgresql in cygwin version:
PostgreSQL 7.3.2 on i686-pc-cygwin, compiled by GCC gcc (GCC) 3.2 20020927
(prerelease)

When delete a record I recive the message :
heap_mark4update: (am)invalid tid

the sql command is:
e.g
delete from irtab where id=29353

What this the problem?

Thanks

Bye !!
Frank Lupo (Wolf) !!

/\_ _/\
\ o o /
--ooo-----ooo---

The same happened to me a while ago, it was not a delete but an update.

Tom Lane posted something about this problem, the error appeared (as far as I can remember) when in the
same command a tuple got modified more than once (because of a join in a one to many relationed
table, for example).

Yours doesn't seem to be the case, but perhaps a trigger is trying to do an update or something.

Anyway, I remember Tom was working on it, I don't know if there is a patch already, but I solved the
problem rewriting the update query in a way that the same tupple didn't get parsed twice.

Hope it helps.