pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Vacuum error
17+ messages / 9 participants
[nested] [flat]

* Vacuum error
@ 2000-09-29 14:47 Hernandez Alvarez Alfredo <ahernand@hafnio.servidores.unam.mx>
  0 siblings, 0 replies; 17+ messages in thread

From: Hernandez Alvarez Alfredo @ 2000-09-29 14:47 UTC (permalink / raw)
  To: pgsql-admin




	Hi. I'm having the following error when i try to vacuum a table:

horde=# vacuum verbose analyze active_sessions;
NOTICE:  --Relation active_sessions-- 
NOTICE:  Pages 144114: Changed 1, reaped 144113, Empty 0, New 0; Tup 3078:
Vac 564305, Keep/VTL 0/0, Crash 0, UnUsed 1046335, MinLen 166, MaxLen
2174; Re-using: Free/Avail. Space 1171699388/1171699388; EndEmpty/Avail.
Pages 0/144113. CPU 19.53s/6.35u sec. 
NOTICE:  Index active_sessions_pkey: Pages 574; Tuples 3078: Deleted
5827. CPU 0.21s/0.37u sec. 
ERROR:  No one parent tuple was found


	Could anyone help me to figure out what is wrong, please???


	thanks in advance



	Ajha






^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* vacuum error
@ 2001-06-14 14:38 brian <webmaster@misanthropia.com>
  0 siblings, 0 replies; 17+ messages in thread

From: brian @ 2001-06-14 14:38 UTC (permalink / raw)
  To: pgsql-admin

Friends,

Help...

I have a small database with a few tables and a view. When I issue the
vacuum command, I get:

ERROR:  cannot read block 5 of pg_description_objoid_index: Input/output
error

Same thing happens when I try pg_dump or pg_dumpall as well. With
pg_dump, I can dump individual tables successfully, but I still get the
error.

Oh yeah, I can vacuum individual tables, no problem.

What can I do?

Thanks,

Brian
-- 
proud to be microsoft free
--



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* vacuum error
@ 2001-06-15 16:37 brian <brian@misanthropia.com>
  2001-06-15 16:58 ` vacuum error Rebi Varghese <rvarghes@aereous.com>
  2001-06-15 18:38 ` Re: vacuum error Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 2 replies; 17+ messages in thread

From: brian @ 2001-06-15 16:37 UTC (permalink / raw)
  To: pgsql-admin

Friends,

Help...

I have a small database with a few tables and a view. When I issue the
vacuum command, I get:

ERROR:  cannot read block 5 of pg_description_objoid_index: Input/output
error

Same thing happens when I try pg_dump or pg_dumpall as well. With
pg_dump, I can dump individual tables successfully, but I still get the
error.

Oh yeah, I can vacuum individual tables, no problem.

What can I do?

Thanks,

Brian
-- 
proud to be microsoft free
--



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* vacuum error
  2001-06-15 16:37 vacuum error brian <brian@misanthropia.com>
@ 2001-06-15 16:58 ` Rebi Varghese <rvarghes@aereous.com>
  1 sibling, 0 replies; 17+ messages in thread

From: Rebi Varghese @ 2001-06-15 16:58 UTC (permalink / raw)
  To: pgsql-admin

Hey guys,

	I am working at a start-up and I need two favors...

1. I need a copy of pgsql for Windows 2000

2. I need a copy for pgsql for openBSD.

	If you guys can direct me to where I can find these... I would be much
appreciative!!

-Rebi


-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org]On Behalf Of brian
Sent: Friday, June 15, 2001 12:37 PM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] vacuum error


Friends,

Help...

I have a small database with a few tables and a view. When I issue the
vacuum command, I get:

ERROR:  cannot read block 5 of pg_description_objoid_index: Input/output
error

Same thing happens when I try pg_dump or pg_dumpall as well. With
pg_dump, I can dump individual tables successfully, but I still get the
error.

Oh yeah, I can vacuum individual tables, no problem.

What can I do?

Thanks,

Brian
--
proud to be microsoft free
--

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly




^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: vacuum error
  2001-06-15 16:37 vacuum error brian <brian@misanthropia.com>
@ 2001-06-15 18:38 ` Tom Lane <tgl@sss.pgh.pa.us>
  1 sibling, 0 replies; 17+ messages in thread

From: Tom Lane @ 2001-06-15 18:38 UTC (permalink / raw)
  To: brian <brian@misanthropia.com>; +Cc: pgsql-admin

brian <brian@misanthropia.com> writes:
> I have a small database with a few tables and a view. When I issue the
> vacuum command, I get:

> ERROR:  cannot read block 5 of pg_description_objoid_index: Input/output
> error

Ugh, sounds like a disk hardware problem :-(.  Better think about new
drives, or at least reformatting the one you have.

As a short-term workaround to be able to dump your DB, I'd suggest just
	DROP INDEX pg_description_objoid_index;
(you'll have to set the magic switch that allows modification of system
tables first).

You could try reindexing pg_description, but since this is a highly
noncritical index, it's probably easier just to get rid of it.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* vacuum error
@ 2002-03-08 16:36 Zhang, Anna <azhang@verisign.com>
  2002-03-08 18:02 ` Re: vacuum error Stephan Szabo <sszabo@megazone23.bigpanda.com>
  2002-03-08 20:05 ` Re: vacuum error Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 2 replies; 17+ messages in thread

From: Zhang, Anna @ 2002-03-08 16:36 UTC (permalink / raw)
  To: pgsql-admin

Hi,
I got an error when vacuum database, see below:

$vacuumdb xdap
ERROR: RelationBuildTriggers: 2 record(s) not found for rel domain.

I deleted triggers that referenced domain before vacuum, is this the cause?
How can I fix it? or It doesn't bother, It's ok to ignore such error?

Thanks in advance!

Anna Zhang



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: vacuum error
  2002-03-08 16:36 vacuum error Zhang, Anna <azhang@verisign.com>
@ 2002-03-08 18:02 ` Stephan Szabo <sszabo@megazone23.bigpanda.com>
  1 sibling, 0 replies; 17+ messages in thread

From: Stephan Szabo @ 2002-03-08 18:02 UTC (permalink / raw)
  To: Zhang, Anna <azhang@verisign.com>; +Cc: pgsql-admin


On Fri, 8 Mar 2002, Zhang, Anna wrote:

> Hi,
> I got an error when vacuum database, see below:
>
> $vacuumdb xdap
> ERROR: RelationBuildTriggers: 2 record(s) not found for rel domain.
>
> I deleted triggers that referenced domain before vacuum, is this the cause?
> How can I fix it? or It doesn't bother, It's ok to ignore such error?

It will be a problem. Update the pg_class row associated with domain to
fix the value of reltriggers, something like:
update pg_class set reltriggers=(select count(*) from pg_trigger
 where tgrelid=pg_class.oid) where relname='domain';





^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: vacuum error
  2002-03-08 16:36 vacuum error Zhang, Anna <azhang@verisign.com>
@ 2002-03-08 20:05 ` Tom Lane <tgl@sss.pgh.pa.us>
  1 sibling, 0 replies; 17+ messages in thread

From: Tom Lane @ 2002-03-08 20:05 UTC (permalink / raw)
  To: Zhang, Anna <azhang@verisign.com>; +Cc: pgsql-admin

"Zhang, Anna" <azhang@verisign.com> writes:
> ERROR: RelationBuildTriggers: 2 record(s) not found for rel domain.

> I deleted triggers that referenced domain before vacuum, is this the cause?

If you deleted them via "delete from pg_trigger" and not by DROP
TRIGGER, then yes.

You'll need to manually fix the value of pg_class.reltriggers for that
table.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: vacuum error
@ 2002-03-08 18:49 Zhang, Anna <azhang@verisign.com>
  2002-03-08 18:53 ` Re: vacuum error Stephan Szabo <sszabo@megazone23.bigpanda.com>
  0 siblings, 1 reply; 17+ messages in thread

From: Zhang, Anna @ 2002-03-08 18:49 UTC (permalink / raw)
  To: 'Stephan Szabo' <sszabo@megazone23.bigpanda.com>; Zhang, Anna <azhang@verisign.com>; +Cc: pgsql-admin

Thanks Stephan! your suggestion works. I just wonder that if dropping
triggers caused such problem, this might be a postgres bug.

Anna Zhang

-----Original Message-----
From: Stephan Szabo [mailto:sszabo@megazone23.bigpanda.com]
Sent: Friday, March 08, 2002 1:02 PM
To: Zhang, Anna
Cc: 'pgsql-admin@postgresql.org'
Subject: Re: [ADMIN] vacuum error



On Fri, 8 Mar 2002, Zhang, Anna wrote:

> Hi,
> I got an error when vacuum database, see below:
>
> $vacuumdb xdap
> ERROR: RelationBuildTriggers: 2 record(s) not found for rel domain.
>
> I deleted triggers that referenced domain before vacuum, is this the
cause?
> How can I fix it? or It doesn't bother, It's ok to ignore such error?

It will be a problem. Update the pg_class row associated with domain to
fix the value of reltriggers, something like:
update pg_class set reltriggers=(select count(*) from pg_trigger
 where tgrelid=pg_class.oid) where relname='domain';



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: vacuum error
  2002-03-08 18:49 Re: vacuum error Zhang, Anna <azhang@verisign.com>
@ 2002-03-08 18:53 ` Stephan Szabo <sszabo@megazone23.bigpanda.com>
  0 siblings, 0 replies; 17+ messages in thread

From: Stephan Szabo @ 2002-03-08 18:53 UTC (permalink / raw)
  To: Zhang, Anna <azhang@verisign.com>; +Cc: pgsql-admin


On Fri, 8 Mar 2002, Zhang, Anna wrote:

> Thanks Stephan! your suggestion works. I just wonder that if dropping
> triggers caused such problem, this might be a postgres bug.

Did you drop them or did you delete from pg_trigger? AFAIK this only
happens with the latter (which isn't meant as normal behavior).




^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* VACUUM Error?
@ 2006-03-07 08:47 Fabrice.Sznajderman@devoteam.com
  2006-03-07 14:52 ` Re: VACUUM Error? Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 17+ messages in thread

From: Fabrice.Sznajderman@devoteam.com @ 2006-03-07 08:47 UTC (permalink / raw)
  To: pgsql-admin

Hello,


I executed a Vacuum on my Postgres database.
You can see the command line : /vacuumdb -f -z -v -d ccm > /tmp/vacuum.txt 
2> /tmp/vacuumError.txt  I used  performed the vacuum.

But I had error :"ERROR:  Parent tuple was not found
vacuumdb: vacuum  ccm failed"
 each time I am executed the vacuum

have you any idea about this error? And may be any solution ?

Thanks in advance,

best regard,

Fabrice
+---------------------------------------------------------------------+
About Devoteam:

Devoteam is an IT consulting group.
Combining consulting and technology solutions offers enables
Devoteam to provide its customers with independent advice and
effective solutions to align their information system's technical
infrastructure with their operational objectives.
The group achieved a turnover of 199 million euros in 2005
an operating margin of 7% and counts 2,100 employees through
12 European countries and the Middle East.
Listed on the Euronext Paris Nouveau Marche and part of the Nexteconomy,
IT CAC, IT CAC 50, SBF 250 index of Euronext Paris.
www.devoteam.com
+---------------------------------------------------------------------+

^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: VACUUM Error?
  2006-03-07 08:47 VACUUM Error? Fabrice.Sznajderman@devoteam.com
@ 2006-03-07 14:52 ` Tom Lane <tgl@sss.pgh.pa.us>
  2006-03-07 15:24   ` Re: VACUUM Error? Fabrice.Sznajderman@devoteam.com
  0 siblings, 1 reply; 17+ messages in thread

From: Tom Lane @ 2006-03-07 14:52 UTC (permalink / raw)
  To: Fabrice.Sznajderman@devoteam.com; +Cc: pgsql-admin

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.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: VACUUM Error?
  2006-03-07 08:47 VACUUM Error? Fabrice.Sznajderman@devoteam.com
  2006-03-07 14:52 ` Re: VACUUM Error? Tom Lane <tgl@sss.pgh.pa.us>
@ 2006-03-07 15:24   ` Fabrice.Sznajderman@devoteam.com
  2006-03-07 15:34     ` Re: VACUUM Error? Andy Shellam <andy.shellam@mailnetwork.co.uk>
  0 siblings, 1 reply; 17+ messages in thread

From: Fabrice.Sznajderman@devoteam.com @ 2006-03-07 15:24 UTC (permalink / raw)
  To: pgsql-admin

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.

                                                 regards, tom lane


+---------------------------------------------------------------------+
About Devoteam:

Devoteam is an IT consulting group.
Combining consulting and technology solutions offers enables
Devoteam to provide its customers with independent advice and
effective solutions to align their information system's technical
infrastructure with their operational objectives.
The group achieved a turnover of 199 million euros in 2005
an operating margin of 7% and counts 2,100 employees through
12 European countries and the Middle East.
Listed on the Euronext Paris Nouveau Marche and part of the Nexteconomy,
IT CAC, IT CAC 50, SBF 250 index of Euronext Paris.
www.devoteam.com
+---------------------------------------------------------------------+

^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: VACUUM Error?
  2006-03-07 08:47 VACUUM Error? Fabrice.Sznajderman@devoteam.com
  2006-03-07 14:52 ` Re: VACUUM Error? Tom Lane <tgl@sss.pgh.pa.us>
  2006-03-07 15:24   ` Re: VACUUM Error? Fabrice.Sznajderman@devoteam.com
@ 2006-03-07 15:34     ` Andy Shellam <andy.shellam@mailnetwork.co.uk>
  2006-03-07 16:09       ` Re: VACUUM Error? Fabrice.Sznajderman@devoteam.com
  2006-03-08 08:23       ` Re: VACUUM Error? Fabrice.Sznajderman@devoteam.com
  2006-03-09 09:00       ` Re: VACUUM Error? Fabrice.Sznajderman@devoteam.com
  0 siblings, 3 replies; 17+ messages in thread

From: Andy Shellam @ 2006-03-07 15:34 UTC (permalink / raw)
  To: Fabrice.Sznajderman@devoteam.com; +Cc: pgsql-admin

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.

                                                  regards, tom lane

!DSPAM:14,440da5fc49411673628609! 

^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: VACUUM Error?
  2006-03-07 08:47 VACUUM Error? Fabrice.Sznajderman@devoteam.com
  2006-03-07 14:52 ` Re: VACUUM Error? Tom Lane <tgl@sss.pgh.pa.us>
  2006-03-07 15:24   ` Re: VACUUM Error? Fabrice.Sznajderman@devoteam.com
  2006-03-07 15:34     ` Re: VACUUM Error? Andy Shellam <andy.shellam@mailnetwork.co.uk>
@ 2006-03-07 16:09       ` Fabrice.Sznajderman@devoteam.com
  2 siblings, 0 replies; 17+ messages in thread

From: Fabrice.Sznajderman@devoteam.com @ 2006-03-07 16:09 UTC (permalink / raw)
  To: pgsql-admin

Hello Andy,

Thanks a lot for your answer,

I'll retry with this new information! 

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.

                                                  regards, tom lane

!DSPAM:14,440da5fc49411673628609! 

+---------------------------------------------------------------------+
About Devoteam:

Devoteam is an IT consulting group.
Combining consulting and technology solutions offers enables
Devoteam to provide its customers with independent advice and
effective solutions to align their information system's technical
infrastructure with their operational objectives.
The group achieved a turnover of 199 million euros in 2005
an operating margin of 7% and counts 2,100 employees through
12 European countries and the Middle East.
Listed on the Euronext Paris Nouveau Marche and part of the Nexteconomy,
IT CAC, IT CAC 50, SBF 250 index of Euronext Paris.
www.devoteam.com
+---------------------------------------------------------------------+

^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: VACUUM Error?
  2006-03-07 08:47 VACUUM Error? Fabrice.Sznajderman@devoteam.com
  2006-03-07 14:52 ` Re: VACUUM Error? Tom Lane <tgl@sss.pgh.pa.us>
  2006-03-07 15:24   ` Re: VACUUM Error? Fabrice.Sznajderman@devoteam.com
  2006-03-07 15:34     ` Re: VACUUM Error? Andy Shellam <andy.shellam@mailnetwork.co.uk>
@ 2006-03-08 08:23       ` Fabrice.Sznajderman@devoteam.com
  2 siblings, 0 replies; 17+ messages in thread

From: Fabrice.Sznajderman@devoteam.com @ 2006-03-08 08:23 UTC (permalink / raw)
  To: pgsql-admin

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" <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.

                                                  regards, tom lane

!DSPAM:14,440da5fc49411673628609! 

+---------------------------------------------------------------------+
About Devoteam:

Devoteam is an IT consulting group.
Combining consulting and technology solutions offers enables
Devoteam to provide its customers with independent advice and
effective solutions to align their information system's technical
infrastructure with their operational objectives.
The group achieved a turnover of 199 million euros in 2005
an operating margin of 7% and counts 2,100 employees through
12 European countries and the Middle East.
Listed on the Euronext Paris Nouveau Marche and part of the Nexteconomy,
IT CAC, IT CAC 50, SBF 250 index of Euronext Paris.
www.devoteam.com
+---------------------------------------------------------------------+

^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: VACUUM Error?
  2006-03-07 08:47 VACUUM Error? Fabrice.Sznajderman@devoteam.com
  2006-03-07 14:52 ` Re: VACUUM Error? Tom Lane <tgl@sss.pgh.pa.us>
  2006-03-07 15:24   ` Re: VACUUM Error? Fabrice.Sznajderman@devoteam.com
  2006-03-07 15:34     ` Re: VACUUM Error? Andy Shellam <andy.shellam@mailnetwork.co.uk>
@ 2006-03-09 09:00       ` Fabrice.Sznajderman@devoteam.com
  2 siblings, 0 replies; 17+ messages in thread

From: Fabrice.Sznajderman@devoteam.com @ 2006-03-09 09:00 UTC (permalink / raw)
  To: pgsql-admin

Victory!!

The Vacuum works well !!! 

Thanks for your help!!!

cheers

Fabrice SZNAJDERMAN

DSI : Application Rendez-Vous - CCM
tel : 01 41 49 60 77
Fabrice Sznajderman/Solutions/FR/Devoteam@Devoteam



"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.

                                                  regards, tom lane

!DSPAM:14,440da5fc49411673628609! 

+---------------------------------------------------------------------+
About Devoteam:

Devoteam is an IT consulting group.
Combining consulting and technology solutions offers enables
Devoteam to provide its customers with independent advice and
effective solutions to align their information system's technical
infrastructure with their operational objectives.
The group achieved a turnover of 199 million euros in 2005
an operating margin of 7% and counts 2,100 employees through
12 European countries and the Middle East.
Listed on the Euronext Paris Nouveau Marche and part of the Nexteconomy,
IT CAC, IT CAC 50, SBF 250 index of Euronext Paris.
www.devoteam.com
+---------------------------------------------------------------------+

^ permalink  raw  reply  [nested|flat] 17+ messages in thread


end of thread, other threads:[~2006-03-09 09:00 UTC | newest]

Thread overview: 17+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-09-29 14:47 Vacuum error Hernandez Alvarez Alfredo <ahernand@hafnio.servidores.unam.mx>
2001-06-14 14:38 vacuum error brian <webmaster@misanthropia.com>
2001-06-15 16:37 vacuum error brian <brian@misanthropia.com>
2001-06-15 16:58 ` vacuum error Rebi Varghese <rvarghes@aereous.com>
2001-06-15 18:38 ` Re: vacuum error Tom Lane <tgl@sss.pgh.pa.us>
2002-03-08 16:36 vacuum error Zhang, Anna <azhang@verisign.com>
2002-03-08 18:02 ` Re: vacuum error Stephan Szabo <sszabo@megazone23.bigpanda.com>
2002-03-08 20:05 ` Re: vacuum error Tom Lane <tgl@sss.pgh.pa.us>
2002-03-08 18:49 Re: vacuum error Zhang, Anna <azhang@verisign.com>
2002-03-08 18:53 ` Re: vacuum error Stephan Szabo <sszabo@megazone23.bigpanda.com>
2006-03-07 08:47 VACUUM Error? Fabrice.Sznajderman@devoteam.com
2006-03-07 14:52 ` Re: VACUUM Error? Tom Lane <tgl@sss.pgh.pa.us>
2006-03-07 15:24   ` Re: VACUUM Error? Fabrice.Sznajderman@devoteam.com
2006-03-07 15:34     ` Re: VACUUM Error? Andy Shellam <andy.shellam@mailnetwork.co.uk>
2006-03-07 16:09       ` Re: VACUUM Error? Fabrice.Sznajderman@devoteam.com
2006-03-08 08:23       ` Re: VACUUM Error? Fabrice.Sznajderman@devoteam.com
2006-03-09 09:00       ` Re: VACUUM Error? Fabrice.Sznajderman@devoteam.com

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox