Re: [BUGS] Re: cannot vacuum a database ! - Mailing list pgsql-general

From Ange Michel POZZO
Subject Re: [BUGS] Re: cannot vacuum a database !
Date
Msg-id 00082918241204.03011@ange.alpinfo.fr
Whole thread Raw
In response to Re: cannot vacuum a database !  (The Hermit Hacker <scrappy@hub.org>)
Responses Re: [BUGS] Re: cannot vacuum a database !  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
ok Hermit Hacker

here is the vacuum verbose :


mydb=> vacuum verbose ;
NOTICE:  --Relation pg_type--
NOTICE:  Pages 2: Changed 0, Reapped 1, Empty 0, New 0; Tup 142: Vac 0, Keep/VTL 0/0, Crash 0, UnUsed 2, MinLen 105,
MaxLen109; Re-using: Free/Avail. Space 256/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec. 
NOTICE:  Index pg_type_typname_index: Pages 4; Tuples 142: Deleted 0. Elapsed 0/0 sec.
NOTICE:  Index pg_type_oid_index: Pages 2; Tuples 142: Deleted 0. Elapsed 0/0 sec.
NOTICE:  --Relation pg_attribute--
NOTICE:  Pages 11: Changed 0, Reapped 1, Empty 0, New 0; Tup 856: Vac 0, Keep/VTL 0/0, Crash 0, UnUsed 2, MinLen 97,
MaxLen97; Re-using: Free/Avail. Space 272/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec. 
NOTICE:  Index pg_attribute_attrelid_index: Pages 7; Tuples 856: Deleted 0. Elapsed 0/0 sec.
NOTICE:  Index pg_attribute_relid_attnum_index: Pages 9; Tuples 856: Deleted 0. Elapsed 0/0 sec.
NOTICE:  Index pg_attribute_relid_attnam_index: Pages 24; Tuples 856: Deleted 0. Elapsed 0/0 sec.
NOTICE:  --Relation pg_proc--
NOTICE:  Pages 26: Changed 0, Reapped 5, Empty 0, New 0; Tup 1022: Vac 7, Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 145,
MaxLen4593; Re-using: Free/Avail. Space 40244/40244; EndEmpty/Avail. Pages 0/5. Elapsed 0/0 sec. 
NOTICE:  Index pg_proc_prosrc_index: Pages 11; Tuples 1021: Deleted 0. Elapsed 0/0 sec.
NOTICE:  Index pg_proc_prosrc_index: NUMBER OF INDEX' TUPLES (1021) IS NOT THE SAME AS HEAP' (1022)
NOTICE:  Index pg_proc_proname_narg_type_index: Pages 17; Tuples 1022: Deleted 0. Elapsed 0/0 sec.
NOTICE:  Index pg_proc_oid_index: Pages 5; Tuples 1022: Deleted 0. Elapsed 0/0 sec.
pqReadData() -- backend closed the channel unexpectedly.
         This probably means the backend terminated abnormally
         before or while processing the request.
We have lost the connection to the backend, so further processing is impossible.  Terminating.
[me@me me]$


If someone has an idea ?

i read in a post archive that a can not recover this error, i must
dump/restore :(

i think id'better upgrade to 7 ... but this is the prod server, i can't shedule
an upgrade like that  for now :(

the database seems to work,  cannot do a vacuum,  but seems to be slower,
so i will upgrade to 7 in 1 or 2 days


thanks

POZZO ANGE


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: 7.1 Release Date
Next
From: Brook Milligan
Date:
Subject: Re: SQL scripts - sequences