VACUUM VERBOSE ANALYZE locking up?? Please help!

From: Wilkinson Charlie E <Charlie(dot)E(dot)Wilkinson(at)irs(dot)gov>
To: pgsql-sql(at)postgresql(dot)org
Cc: cwilkins(at)boinklabs(dot)com
Subject: VACUUM VERBOSE ANALYZE locking up?? Please help!
Date: 2001-10-10 20:46:53
Message-ID: 36E747F41E90D411A6CC0004AC3699EB058049B8@nct0010mb03.nc.no.irs.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Ok it doesn't kill the whole backend, but VACUUM... comes
to a halt partway through and it's necessary to ^C out
of the transaction in psql. Sometimes trying again will
work, mostly that doesn't work. Restarting the backend
and then doing the VACUUM... will usually result in
success. I was having this problem in 7.0.something and
it's still happening in 7.1.3 (built from scratch on a
Redhat 6.2 box). I used pg_dumpall to migrate the data.
I've made a serious effort to hunt the web for a clue with no
real success.

Here's what I get:

cwilkins=# vacuum verbose analyze;
NOTICE: --Relation pg_type--
NOTICE: Pages 4: Changed 0, reaped 1, Empty 0, New 0; Tup 244: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed 26, MinLen 106, MaxLen 109; Re-using:
Free/Avail. Space 4472/0; EndEmpty/Avail. Pages 0/0. CPU 0.00s/0.00u
sec.
NOTICE: Index pg_type_oid_index: Pages 2; Tuples 244: Deleted 0. CPU
0.00s/0.00u sec.
NOTICE: Index pg_type_typname_index: Pages 4; Tuples 244: Deleted 0.
CPU 0.00s/0.00u sec.
NOTICE: Analyzing...
NOTICE: --Relation pg_attribute--
NOTICE: Rel pg_attribute: TID 24/20: DeleteTransactionInProgress 0 -
can't shrink relation
NOTICE: Rel pg_attribute: TID 24/21: DeleteTransactionInProgress 0 -
can't shrink relation
NOTICE: Rel pg_attribute: TID 24/22: DeleteTransactionInProgress 0 -
can't shrink relation
NOTICE: Rel pg_attribute: TID 24/23: DeleteTransactionInProgress 0 -
can't shrink relation
NOTICE: Rel pg_attribute: TID 24/24: DeleteTransactionInProgress 0 -
can't shrink relation
NOTICE: Rel pg_attribute: TID 24/25: DeleteTransactionInProgress 0 -
can't shrink relation
[[[etc... etc... snip...]]]
NOTICE: Index pg_rewrite_oid_index: Pages 2; Tuples 11: Deleted 0. CPU
0.00s/0.00u sec.
NOTICE: Index pg_rewrite_rulename_index: Pages 2; Tuples 11: Deleted 0.
CPU 0.00s/0.00u sec.
NOTICE: --Relation pg_toast_17058--
NOTICE: Pages 1: Changed 0, reaped 1, Empty 0, New 0; Tup 2: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed 3, MinLen 834, MaxLen 2034; Re-using:
Free/Avail. Space 5280/0; EndEmpty/Avail. Pages 0/0. CPU 0.01s/0.00u
sec.
NOTICE: Index pg_toast_17058_idx: Pages 2; Tuples 2: Deleted 0. CPU
0.00s/0.00u sec.
[[[query stops here and will go no further]]]

Any useful insights or solutions? Pretty please? :)

Thanks for any help,
Charlie

(Apologies in advance if this message has any HTML component.
I've told ^%$#(at)! Outlook as loudly as possible PLAIN TEXT ONLY!)
--
Charlie Wilkinson
TRIS Development Systems Administrator
M:I:SD:CT:CC:TD
Phone: 202-283-3241
MSMail: Charlie(dot)E(dot)Wilkinson(at)irs(dot)gov
SMTP: cwilkins(at)tris(dot)irs(dot)gov
Home: cwilkins(at)boinklabs(dot)com
This message constructed from 90% post-consumer electrons.

Browse pgsql-sql by date

  From Date Subject
Next Message Aasmund Midttun Godal 2001-10-10 21:07:27 Restricting access to large objects.
Previous Message Aasmund Midttun Godal 2001-10-10 20:18:59 Restricting access to Large objects