Hello Andy,

I tried last night, the way which you suggested me.. I looked at the log file of the vacuum process... and there is no error..
I tried to run the vacuum without the -f option , last night.

So to the next night, I will add the -f option and will run again the vacuum process.

Thanks again for your help!

I will give you a feedback!

Best regard

Fabrice





"Andy Shellam" <[EMAIL PROTECTED]>
Envoyé par : [EMAIL PROTECTED]

07/03/2006 16:34

Veuillez répondre à
<[EMAIL PROTECTED]>

A
<[EMAIL PROTECTED]>
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
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 <[EMAIL PROTECTED]>

07/03/2006 15:52


A
[EMAIL PROTECTED]
cc
pgsql-admin@postgresql.org
Objet
Re: [ADMIN] VACUUM Error?







[EMAIL PROTECTED] 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!

Reply via email to