Re: VACUUM Error?

If you do "ps auxwww|grep postgres" on your console command line - you
should find processes with a status of "IDLE IN TRANSACTION" or similar, and
use that data and the PG server status to identify where it came from, and
submit a COMMIT or ROLLBACK command on that connection.

_____

From: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of
Fabrice(dot)Sznajderman(at)devoteam(dot)com
Sent: Tuesday, 07 March, 2006 3:25 pm
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] VACUUM Error?

Hello Tom Lane,

Thank you very much for your answer!!

My PG version is older than 7.3 , I know it so old and so much old.. but I
can't update this version... :-((

However, could you explain me how I can close open transaction?

Thanks in advance!!

best regard

Fabrice

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>

07/03/2006 15:52

A
Fabrice(dot)Sznajderman(at)devoteam(dot)com

cc
pgsql-admin(at)postgresql(dot)org

Objet
Re: [ADMIN] VACUUM Error?

Fabrice(dot)Sznajderman(at)devoteam(dot)com writes:
> But I had error :"ERROR: Parent tuple was not found

What PG version is this? We recently fixed some bugs that could lead to
this error.

The error could only occur if you have some old open transaction(s) that
could possibly still see since-updated tuples in the vacuumed table.
So it'll go away if you close out open transactions.

regards, tom lane

!DSPAM:14,440da5fc49411673628609!