I will give you feedback when I would had made this new way !
Best regard
Fabrice
"Andy Shellam" <andy.shellam@mailnetwork.co.uk> Envoyé par : pgsql-admin-owner@postgresql.org
07/03/2006 16:34
Veuillez répondre à <andy.shellam@mailnetwork.co.uk>
A
<Fabrice.Sznajderman@devoteam.com>
cc
Objet
Re: [ADMIN] 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@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Fabrice.Sznajderman@devoteam.com Sent: Tuesday, 07 March, 2006 3:25 pm To: pgsql-admin@postgresql.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@sss.pgh.pa.us>
07/03/2006 15:52
A
Fabrice.Sznajderman@devoteam.com
cc
pgsql-admin@postgresql.org
Objet
Re: [ADMIN] VACUUM Error?
Fabrice.Sznajderman@devoteam.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.
